Loading...
Loading...
Found 111 Skills
Extract learnings about skill creation/improvement from a session and propagate them to the central skill learnings file, then sync to appropriate skills. Use when a session revealed patterns, anti-patterns, or insights about structuring skills. Invoke via /update-skill-learnings or after skill creation/improvement sessions.
Conversational briefing on your recent reading — what you finished, what you highlighted, and what you had to say about it
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
Salesforce Data Cloud Segment phase. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use sf-datacloud-harmonize), activation work (use sf-datacloud-act), query/search-index work (use sf-datacloud-retrieve), or STDM/session tracing (use sf-ai-agentforce-observability).
Route spec content into the correct delta spec file. Reads .spec-driven/specs/INDEX.md first, then decides whether to update an existing spec file, create a new spec file, create a new category, modify requirements, or remove specific requirements.
하네스 시스템 안내 전문가. "어떤 스킬", "어떻게", "도움말", "help", "가이드", "어디서 시작" 키워드로 트리거. 스킬 추천, 워크플로우 안내, 시스템 개념 설명을 제공하는 읽기전용 온보딩 스킬. (skills.sh 글로벌 설치 안내 포함)
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. Routes to type-specific guidance (generic flowchart, architecture flowchart) and tells you when to proceed directly, when to use a different diagram type, or when the tool isn't the right fit at all.
Create a GitHub issue with title and description. Use when the user wants to file a bug, request a feature, or create a tracking issue.
Use when generating, updating, or organizing documentation (component/API docs, project indexes, diagrams, tutorials, learning paths) - provides structured workflows and references for docs generation, indexing, diagrams, and teaching.
Create and manage Architecture Decision Records (ADRs). Use when documenting technology choices, design decisions, or architectural changes that need to be tracked over time. This is the CANONICAL ADR skill - all ADR-related work should use this skill.
Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.