steelmorgan/agent-development
framework_eng/skills/framework-meta/agent-development/SKILL.md
Create or configure custom subagents with specialized prompts (reviewers, debuggers, domain-specific assistants). Helps determine the location, structure, and system context of a new agent.
$ install --global
skillsauthnpx skillsauth add steelmorgan/1c-agent-based-dev-framework agent-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 5:55 AM401.8s1 file scanned
SKILL.md
- name:
- agent-development
- description:
- Create or configure custom subagents with specialized prompts (reviewers, debuggers, domain-specific assistants). Helps determine the location, structure, and system context of a new agent.
Creating Custom Subagents
Subagents are specialized AI assistants running in isolated contexts with custom system prompts. If previous conversation context exists, infer the subagent's purpose from what was discussed.
Subagent Locations
| Location | Scope | Priority |
|----------|-------|----------|
| .cursor/agents/ | Current project | Higher |
| ~/.cursor/agents/ | All your projects | Lower |
When multiple subagents share the same name, the higher-priority location wins.
Project subagents (.cursor/agents/): Ideal for codebase-specific agents. Check into version control to share with your team.
User subagents (~/.cursor/agents/): Personal agents available across all your projects.
Subagent File Format
Create a .md file with YAML frontmatter and a markdown body (the system prompt):
---
name: code-reviewer
description: Reviews code for quality and best practices
---
You are a code reviewer. When invoked, analyze the code and provide
specific, actionable feedback on quality, security, and best practices.
Required Fields
| Field | Description |
|-------|-------------|
| name | Unique identifier (lowercase letters and hyphens only) |
| description | When to delegate to this subagent (be specific!) |
Writing Effective Descriptions
The description is critical - the AI uses it to decide when to delegate. Include "use proactively" to encourage automatic delegation.
# Bad — too vague
description: Helps with code
# Good — specific trigger conditions
description: Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
Example Subagent
---
name: code-reviewer
description: Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
---
You are a senior code reviewer ensuring high standards of code quality and security.
When invoked:
1. Run git diff to see recent changes
2. Focus on modified files
3. Begin review immediately
Review checklist:
- Code is clear and readable
- Functions and variables are well-named
- No duplicated code
- Proper error handling
- No exposed secrets or API keys
- Input validation implemented
- Good test coverage
- Performance considerations addressed
Provide feedback organized by priority:
- Critical issues (must fix)
- Warnings (should fix)
- Suggestions (consider improving)
Include specific examples of how to fix issues.
Subagent Creation Workflow
- Decide scope: project (
.cursor/agents/) or user (~/.cursor/agents/) - Create file:
mkdir -p .cursor/agents && touch .cursor/agents/my-agent.md - Write frontmatter:
nameanddescription(required) - Write system prompt: what to do when invoked, workflow, output format, constraints
- Test: ask the AI to use the new subagent
Best Practices
- Each subagent should excel at one specific task
- Include trigger terms in descriptions so the AI knows when to delegate
- Check project subagents into version control
- Include "use proactively" in descriptions
Troubleshooting: Subagent Not Found
- File must be in
.cursor/agents/or~/.cursor/agents/ - File must have
.mdextension - YAML frontmatter syntax must be valid
depends_on: []
Related Skills
steelmorgan/source-of-truth
testing
VerifiedTrustedCommunity
MUST use BEFORE making a judgment about the cause of a conflict, a test failure, or an artifact dispute. Defines the end-to-end verification method L1→L6 and the classification of the first broken link.
69SKILL.mdUpdated Jun 13, 2026
steelmorgan/skill-learning
development
VerifiedTrustedCommunity
MUST use AFTER a work cycle with ≥2 iterations (wrote → error → fixed → success). Provides the retrospective procedure and the format for recording practice/anti-patterns in references/learned-patterns.md or {project}/.context/learned-patterns.md.
69SKILL.mdUpdated Jun 13, 2026
steelmorgan/rlm-workflow
tools
VerifiedTrustedCommunity
MUST use WHEN you are writing reusable knowledge into RLM (pattern / architectural decision / stable domain fact) OR reading it before a non-trivial task/solution in the domain. Provides the breakdown of native-push vs RLM-pull, tools for writing and reading RLM, H-MEM levels, and hygiene.
69SKILL.mdUpdated Jun 13, 2026
steelmorgan/quick-fix
testing
VerifiedTrustedCommunity
MUST use WHEN the task is classified as simple (< 20 lines, 1 file, no new metadata objects, no architectural decisions). Provides a short cycle of 3 steps with a guard on the self path and mandatory verify.
69SKILL.mdUpdated Jun 13, 2026