agent-architecture-analysis
Use when auditing an agent codebase against the 12-Factor Agents methodology, reviewing LLM-powered system architecture, or assessing agentic app compliance. Triggers on "analyze agent architecture", "12-factor audit", "how compliant is this agent", or "evaluate this LLM app". Also applies when comparing frameworks or planning agent improvements. Not for quick checklists — this performs deep per-factor codebase analysis with file-level evidence.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/anderskev/agent-architecture-analysisWhat This Skill Does
The agent-architecture-analysis skill provides a systematic framework for auditing AI-powered agentic systems against the 12-Factor Agents methodology. This skill parses your codebase to evaluate how your application handles structural concerns like natural language-to-tool conversion, prompt management, and context window optimization. By automating the search for specific patterns—such as Pydantic schema usage, Jinja2 template implementations, and custom message serialization—the skill identifies architectural drift and provides actionable compliance ratings (Strong, Partial, Weak) to help you improve system reliability and maintainability.
Installation
You can install this skill directly via the OpenClaw CLI using the following command:
clawhub install openclaw/skills/skills/anderskev/agent-architecture-analysis
Use Cases
- Architectural Audits: Evaluate the robustness of an LLM-based system before a major release.
- Technical Debt Assessment: Identify hardcoded prompts and unvalidated model outputs that could cause runtime failures.
- Onboarding/Review: Quickly understand the structure of a new agentic codebase by seeing how it handles context and tool calling.
- CI/CD Integration: Incorporate agent compliance checks into your build pipeline to prevent the introduction of weak prompt management or unvalidated outputs.
Example Prompts
- "Analyze my project in
/home/user/code/customer-support-agentand tell me which factors are currently rated as Weak." - "Perform a 12-factor audit on the codebase at
./srcand focus specifically on how we handle prompt versioning." - "Run a compliance check on my agent architecture and generate a summary of anti-patterns found in the
prompts/directory."
Tips & Limitations
- Tips: For best results, ensure your project follows standard Python naming conventions. Use the
docs_pathparameter if you have pre-existing architectural documentation to allow the agent to cross-reference code with design intent. - Limitations: This skill performs static analysis based on grep patterns and heuristics. It cannot execute the code to observe runtime behavior. Complex dynamic prompt generation or highly obfuscated code may yield false negatives. Always review the detailed logs generated by the skill to verify compliance classifications.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-anderskev-agent-architecture-analysis": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read
Related Skills
explanation-docs
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
tutorial-docs
Tutorial patterns for documentation - learning-oriented guides that teach through guided doing
pytest-code-review
Reviews pytest test code for async patterns, fixtures, parametrize, and mocking. Use when reviewing test_*.py files, checking async test functions, fixture usage, or mock patterns.
reference-docs
Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.
serde-code-review
Reviews serde serialization code for derive patterns, enum representations, custom implementations, and common serialization bugs. Use when reviewing Rust code that uses serde, serde_json, toml, or any serde-based serialization format. Covers attribute macros, field renaming, and format-specific pitfalls.