Loading...
Loading...
Found 39 Skills
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.
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.
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 asks to "generate an AGENTS.md", "create a CLAUDE.md", "write agent instructions", "set up AGENTS.md", "make an AGENTS.md for this repo", "configure agent behavior", or mentions generating, writing, or improving an AGENTS.md or CLAUDE.md file for a project.
Guide for creating effective agent skills. Use PROACTIVELY when creating new skills or refactoring bloated ones. Teaches progressive disclosure, 200-line rule, and 3-tier loading system.
Standardized patterns for how agents discover, reference, and compose skills using progressive disclosure architecture
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.
Create, audit, and maintain CLAUDE.md documentation files that configure Claude Code for projects. Use this skill when (1) initializing a new project with Claude Code configuration, (2) reviewing or improving existing CLAUDE.md files, (3) organizing project instructions using progressive disclosure patterns, (4) converting repeated instructions into permanent documentation, or (5) setting up agent_docs/ structures for larger codebases. Handles the WHAT/WHY/HOW framework, conciseness optimization, and file import patterns.
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.
Expert AGENTS.md file assistant. Use when users want to create, verify, or improve AGENTS.md files. Helps with creating minimal, focused AGENTS.md files following progressive disclosure principles, verifying existing files for issues (bloat, contradictions, stale info), and refactoring bloated files.