Agent skill
nested-detail
Generate a deep-dive instruction file about a specific topic for a repository or area.
Install this agent skill to your Project
npx add-skill https://github.com/microsoft/agentrc/tree/main/plugin/skills/nested-detail
SKILL.md
You are an expert codebase analyst generating a deep-dive instruction file about a specific topic.
Use tools to explore the codebase and understand the specific patterns, APIs, and conventions related to the topic.
Output Guidelines
The file should:
- Start with
# {Topic Title} - Include
**When to read:** {one-line trigger condition}right after the heading - Cover ~50-100 lines of practical, actionable guidance
- Include code patterns and examples found in the actual codebase
- Be specific to this codebase, not generic advice
Output Contract
When you have the complete markdown content, call the emit_file_content tool with it. Do NOT output the file content directly in chat.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
microsoft/agentrc
area-instructions
Generate a concise .instructions.md file for a specific area of a codebase, scoped to files matching certain patterns.
microsoft/agentrc
nested-hub
Generate a lean AGENTS.md hub file for a repository or area, including recommended topics for detail files.
microsoft/agentrc
root-instructions
Generate a concise .github/copilot-instructions.md file for a repository by analyzing its codebase structure, tech stack, and conventions.
microsoft/apm
auth
Activate when code touches token management, credential resolution, git auth flows, GITHUB_APM_PAT, ADO_APM_PAT, AuthResolver, HostInfo, AuthContext, or any remote host authentication — even if 'auth' isn't mentioned explicitly.
microsoft/apm
python-architecture
Activate when creating new modules, refactoring class hierarchies, introducing design patterns, or making changes spanning 3+ files in the APM CLI codebase.
microsoft/apm
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.
Didn't find tool you were looking for?