Explorar skills

Utilize para construir, depurar ou estender fluxos de trabalho n8n, incluindo a geração de JSON de fluxo de trabalho, a criação de nós TypeScript personalizados, a construção de agentes de IA, a iteração de itens, a escrita de JS para Code-node, a lintagem de fluxos de trabalho, o diagnóstico de execuções falhas ou o controle de instâncias n8n ativas via REST.

Compress agent outputs for efficient context handoff between pipeline nodes while preserving actionable information

구조화된 리서치 수행. 주제별 깊이(quick/standard/deep) 선택, 병렬 수집, 신뢰도 등급 부여, 마크다운 리포트 생성.

Bridge Claude Code and Codex for bidirectional execution review. Use when Claude should send its result to Codex/GPT-5.5 for audit, audit Codex/GPT-5.5 handoffs, return feedback to Codex, or run an automated Claude-Codex review loop.

Gate ② 质量门禁。README risk Q2 走 RC，Q3 串行走 R1、R2、R3；reviewer 一轮列全发现并交 x-fix 批量修复。

Analyze survey CSV files and extract quantitative frequencies, qualitative themes, and Top-3 insights. No Python required — Cowork-native. Use when reviewing Google Forms/Typeform/SurveyMonkey exports, preparing stakeholder reports, or turning raw survey data into actionable findings. Triggers: 'analyze survey results', 'survey results analyzer', 'проанализируй результаты опроса', 'анализ опроса'.

화면 단위 E2E 테스트 자동화. Figma/코드 기반 테스트 케이스 도출 → Playwright 코드 생성 → Forge Loop(에스컬레이션 기반 자율 실행). "E2E 돌려줘", "화면 테스트 만들어줘", "이 페이지 자동 테스트" 등의 요청에 사용.

This skill should be used when writing commits, PRs, or comments that will be visible to OSS maintainers — it covers the no-AI-attribution rule, AI-tell avoidance in writing, and the situations where a human contributor should respond instead of the AI tool. Sibling to oss-contribution and pr-etiquette.

교차 모델 토론. Agent Teams / Codex CLI / self-debate 모드 선택. 설계 결정, 아키텍처 선택 시 활용. "어느 쪽이 나을까", "설계 비교해줘", "토론시켜줘", "교차 검증해줘" 등의 요청에 사용.

Canvas API Connection Skill

Generate C4 Container diagrams (Simon Brown standard) as editable .drawio XML files. Use when the user asks for architecture diagrams, system diagrams, C4 diagrams, container diagrams, or wants to visualize system architecture. Also use proactively when explaining systems with 3+ components where a visual would clarify the architecture.

Compare two document versions and produce a structured changelog — no git needed. Use for PRDs, SOPs, contracts, strategy docs. Triggers: 'compare these two documents', 'what changed between versions', 'generate a changelog', 'сравни две версии документа', 'что изменилось', 'сделай changelog'.