
Agent Development Principles
- 17 installs
- 3 repo stars
- Updated July 2, 2026
- akillness/oh-my-gods
agent-development-principles is a compatibility-alias skill that routes to the canonical agent-principles skill while preserving the legacy exact-name reference.
About
This is a compatibility alias skill that exists only to preserve older references to the name agent-development-principles. It acknowledges the legacy name and routes the substantive collaboration-principles work to the canonical agent-principles skill. A developer encounters it when a legacy install script, README, or workflow still names this exact skill.
- Compatibility alias that routes to the canonical agent-principles skill
- Preserves exact-name references in legacy install docs and workflows
- Kept intentionally narrow so it does not compete as a peer default
Agent Development Principles by the numbers
- 17 all-time installs (skills.sh)
- Ranked #10,886 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
agent-development-principles capabilities & compatibility
- Capabilities
- agent configuration · agent workflow
What agent-development-principles says it does
Compatibility alias for `agent-principles`.
This skill remains only for compatibility with older docs, installs, and
npx skills add https://github.com/akillness/oh-my-gods --skill agent-development-principlesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 17 |
|---|---|
| repo stars | ★ 3 |
| Last updated | July 2, 2026 |
| Repository | akillness/oh-my-gods ↗ |
What it does
Preserve backward compatibility for the legacy agent-development-principles name while routing real work to agent-principles.
Who is it for?
Skip if: Serving as the default principles skill or a second peer principles guide
When should I use this skill?
A legacy install script, README, or workflow still references the exact name agent-development-principles
By the numbers
- 3-step instruction (recognize alias, preserve name, route to canonical)
Files
Agentic Development Principles Alias
This skill remains only for compatibility with older docs, installs, and exact-name references.
When to use this skill
- The user explicitly asks for
agent-development-principles - A legacy install script, README, or workflow still depends on this exact name
- You need to preserve backward compatibility while routing real work to the
canonical principles skill
Instructions
Step 1: Recognize this as a legacy alias
- Treat
agent-development-principlesas a compatibility surface, not the
default principles skill.
- Keep the answer short and route the substantive work to
agent-principles.
Step 2: Preserve exact-name compatibility
- If a README, install command, or older workflow explicitly names this skill,
acknowledge the exact-name match and continue without breaking the flow.
- Do not expand this alias into a second peer principles guide.
Step 3: Route to the canonical skill
- Use
agent-principlesfor the real collaboration-principles guidance. - Keep this alias narrow so the catalog has one default skill for this job.
Examples
Example 1: Exact-name request
Input:
Use agent-development-principles to explain how I should collaborate with AI agents.Output shape:
- acknowledges the legacy skill name
- routes the substantive answer to
agent-principles - keeps compatibility intact without duplicating the whole guide
Best practices
- Keep compatibility aliases narrow and explicit
- Preserve old install surfaces without letting the alias compete as a peer default
- Update discovery copy so maintainers know which skill is canonical
References
- ../agent-principles/SKILL.md
- Claude Code Best Practices
- ykdojo claude-code-tips
- Ado's Advent of Claude
{
"skill_name": "agent-development-principles",
"evals": [
{
"id": 1,
"prompt": "Use agent-development-principles to explain the core habits for working with AI coding agents.",
"expected_output": "A compatibility-aware answer that recognizes the exact legacy skill name and routes the substantive guidance to the canonical `agent-principles` skill.",
"assertions": [
"Response acknowledges `agent-development-principles` as an exact-name or legacy surface",
"Response routes the substantive collaboration-principles work to `agent-principles`",
"Response does not duplicate the full canonical guide inside the alias"
]
},
{
"id": 2,
"prompt": "My old install docs still say to use agent-development-principles. Is that still valid?",
"expected_output": "A compatibility answer that preserves the old name while clarifying that `agent-principles` is the canonical skill.",
"assertions": [
"Response preserves backward compatibility",
"Response identifies `agent-principles` as the canonical skill",
"Response avoids treating both skills as equal defaults"
]
}
]
}
N:agent-development-principles
D:Compatibility alias for agent-principles. Use when an existing workflow, install surface, or exact-name request still references agent-development-principles; substantive collaboration-principles work should route to agent-principles.
G:agentic-development principles context-management automation ai-collaboration
U[4]:
Preserve exact-name compatibility for old docs and installs
Recognize the legacy agent-development-principles name
Route substantive principles guidance to agent-principles
Keep duplicate catalog competition low
R[3]:
Do not compete with the canonical skill as a peer default
Keep the alias brief and explicit
Preserve backward compatibility without duplicating the full guide
S[3]{n,action}:
1,Recognize the request as a legacy alias surface
2,Preserve exact-name compatibility
3,Route the substantive work to agent-principles