Loading...
Loading...
Found 48 Skills
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
Unified Exa research skill using get_code_context_exa and web_search_advanced_exa. Use for code/API snippet lookup, company research, people/LinkedIn research, financial report search, research paper search, personal site search, and X/Twitter tweet search. Follow progressive disclosure: load only the relevant reference file(s) for the user intent.
This skill should be used when the user asks to "create a skill", "write a new skill", "add a skill", "SKILL.md format", "skill frontmatter", or needs guidance on skill structure, progressive disclosure, or OpenCode skill development.
The foundational context engineering skill — start here when exploring the discipline. This skill should be used when the user asks to "understand context", "explain context windows", "design agent architecture", "debug context issues", "optimize context usage", or discusses context components, attention mechanics, progressive disclosure, or context budgeting. Also activates when the user mentions "context engineering" or "context-engineering" for foundational understanding of AI agent context systems.
Guide for Writing and Optimizing AGENTS.md, following the principle of progressive disclosure. This skill must be loaded when users create, modify, or refactor AGENTS.md, discuss AI agent instruction structures, rule placement, or mention terms like "progressive disclosure", "modularity", "AGENTS.md best practices". Even if users simply say "help me write an AGENTS.md", "optimize this configuration file", or "split the rules", this skill should be used.
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
Create, optimize, and maintain AGENTS.md and CLAUDE.md files using progressive disclosure. Use when: User wants to create AGENTS.md/CLAUDE.md, optimize existing AI documentation, implement progressive disclosure, detect project structure (monorepo/polyrepo), or prevent documentation bloat. Triggers on: "create agents.md", "update AGENTS.md", "AI documentation", "project context", "monorepo documentation", "progressive disclosure", "Claude Code context", or when AI repeatedly asks the same questions about the project.
This skill should be used when the user says "update CLAUDE.md", "refresh CLAUDE.md", "sync CLAUDE.md with the codebase", "reorganize CLAUDE.md", "optimize project instructions", or when CLAUDE.md is stale, verbose, or out of sync.
This skill should be used when the user asks to "create a skill", "build a skill", "write a skill", "improve skill structure", "understand skill creation", or mentions SKILL.md files, skill development, progressive disclosure, XML structure, or bundled resources (scripts, references, assets). Comprehensive guide for creating effective Claude Code skills.
Creates well-structured Agent Skills following best practices. Use when building new skills for Claude Code, designing skill directory structures, writing SKILL.md files, or improving existing skills with progressive disclosure patterns.
Comprehensive knowledge of all 23 Gang of Four design patterns with progressive disclosure (Quick/Practical/Deep), pattern recognition for problem-solving, and philosophy-aligned guidance to prevent over-engineering.
Navigation and user flow patterns including routing, state management, progressive disclosure, and game progression. Use when designing multi-step flows, game phases, or navigation structures. (project)