Standards analysis
Use this skill for complex problem analysis, architectural decisions, bug investigation, or requirement gathering. Provides decomposition and trade-off frameworks.From its SKILL.md
npx -y skills add pecigonzalo/agent-skills --skill standards-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.5 KB, 760 tokens by cl100k_base, as published. Nobody here has run it
Analysis Standards
Provides: Problem decomposition techniques, requirement gathering checklists, trade-off analysis frameworks, and analysis report templates.
Quick Reference
Process: Context → Gather → Patterns → Impact → Recommendations
Report Format: Context, Findings, Patterns, Issues (🔴🟡🔵), Recommendations, Trade-offs, Next Steps
Be: Thorough, Objective, Specific, Actionable
Checklist: Context stated, Evidence gathered, Patterns identified, Issues prioritized, Recommendations specific, Trade-offs considered
Purpose
Framework for analyzing code, patterns, and technical issues systematically.
When to Use
Reference this when:
- Analyzing codebase patterns
- Investigating bugs or issues
- Evaluating architectural decisions
- Assessing code quality
- Researching solutions
Analysis Process
1. Understand Context
- What are we analyzing and why?
- What's the goal or question?
- What's the scope?
- What constraints exist?
2. Gather Information
- Read relevant code / data points
- Check documentation
- Search for patterns
- Review related issues
- Examine dependencies
3. Identify Patterns
- What's consistent across the codebase?
- What conventions are followed?
- What patterns are repeated?
- What's inconsistent or unusual?
4. Assess Impact
- What are the implications?
- What are the trade-offs?
- What could break?
- What are the risks?
5. Provide Recommendations
- What should be done?
- Why this approach?
- What are alternatives?
- What's the priority?
Analysis Report Format
## Analysis: {Topic}
**Context:** {What we're analyzing and why}
**Findings:**
- {Key finding 1}
- {Key finding 2}
- {Key finding 3}
**Patterns Observed:**
- {Pattern 1}: {Description}
- {Pattern 2}: {Description}
**Issues Identified:**
- 🔴 Critical: {Issue requiring immediate attention}
- 🟡 Warning: {Issue to address soon}
- 🔵 Suggestion: {Nice-to-have improvement}
**Recommendations:**
1. {Recommendation 1} - {Why}
2. {Recommendation 2} - {Why}
**Trade-offs:**
- {Approach A}: {Pros/Cons}
- {Approach B}: {Pros/Cons}
**Next Steps:**
- {Action 1}
- {Action 2}
Common Analysis Types
Code Quality Analysis
- Complexity (cyclomatic, cognitive)
- Duplication
- Test coverage
- Documentation completeness
- Naming consistency
- Error handling patterns
Architecture Analysis
- Module dependencies
- Coupling and cohesion
- Separation of concerns
- Scalability considerations
- Performance bottlenecks
Bug Investigation
- Reproduce the issue
- Identify root cause
- Assess impact and severity
- Propose fix with rationale
- Consider edge cases
Pattern Discovery
- Search for similar implementations
- Identify common approaches
- Document conventions
- Note inconsistencies
- Recommend standardization
Best Practices
Be Thorough
- Check multiple examples
- Consider edge cases
- Look for exceptions
- Verify assumptions
Be Objective
- Base conclusions on evidence
- Avoid assumptions
- Consider multiple perspectives
- Acknowledge limitations
Be Specific
- Provide concrete examples
- Include file names and line numbers
- Show code snippets
- Quantify when possible
Be Actionable
- Clear recommendations
- Prioritize findings
- Explain rationale
- Suggest next steps
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most research analysis skills give in 760 tokens
Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07
- Generate a markdown reportin 32 of 1063, across 23 files
- Cite each claim's sourcein 30 of 1063, across 15 files
- Define the ideal customer profilein 20 of 1063, across 2 files
- Search for companies matching the criteriain 20 of 1063, across 2 files
- Assign a fit score from one to tenin 20 of 1063, across 2 files
- Analyze the codebase to understand the productin 19 of 1063, across 1 file
- Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
- Look for signals of immediate needin 19 of 1063, across 1 file
- Identify the target decision maker rolein 19 of 1063, across 1 file
- Suggest a personalized contact strategyin 19 of 1063, across 1 file
- Provide conversation starters for outreachin 19 of 1063, across 1 file
- Format results in a scannable markdown templatein 19 of 1063, across 1 file
Said here and by no other author read
- state the context scope and constraints
- gather evidence from code and documentation
- assess impact trade-offs and risks
- base conclusions on evidence without assumptions
- quantify findings when possible
- prioritize identified issues
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.