analyze
Skill2 starsChanged 6 months agoMITView on GitHub
Deep analysis workflow for codebases, architectures, systems, products, markets, or research topics. Use when the user asks to analyze, investigate, assess, evaluate, compare, or research something in a structured way.
74 other projects use a version of this.
Adopted by
Most recently taken up by
- mikeleg/skillstheir own version, first seen Nov 16, 2026
- Imtylerrrrrr/second-braintheir own version, first seen Nov 16, 2026
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- codeboehm/maximtheir own version, first seen Nov 15, 2026
- link7373/agentic-bi-teamtheir own version, first seen Nov 10, 2026
Used with
Projects with it also use constitution, revise and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ArvorCoSkillconstitution
Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.
Also in 4 projects that use this
Renozoic-FoundrySkillrevise
Revise an existing spec based on feedback or correction
Also in 3 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 3 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 5 projects that use this
DockerSkillwrite
Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.
Also in 6 projects that use this
woosikkimSkillcancel
Clear any stale OMC-Slim state
Also in 3 projects that use this
- +1 more from ArvorCo
Other versions74 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 74
- anthropics/knowledge-work-plugins★ 36ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- oxsecurity/megalinter★ 2.7ksame name
- H-mmer/pentest-agents★ 815same name
- hardisgroupcom/sfdx-hardis★ 437same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- nwiizo/tfmcp★ 373same name
- hsantanna88/clo-author★ 262same name
- hugosantanna/clo-author★ 262same name
- ansvisor/ansvisor★ 241same name
64 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read AGENTS.md at the project root to understand the project's domain, tech stack, and business context.
- Distinctive: line 51
Use the minimum set of relevant sources:
- Distinctive: line 65
Consider at least one alternative explanation
- Very specific: line 71
Use output-templates.md to structure the output.
- Distinctive: line 73
All outputs should include:
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Analyze
Perform structured analysis with explicit scope, evidence, and conclusions.
0. Gather Context
Read AGENTS.md at the project root to understand the project's domain, tech stack, and business context. This shapes framework selection and analysis scope.
1. Classify the Request
Identify:
- Subject
- Core question
- Scope
- Desired depth
- Audience
- Decision the analysis should inform
2. Choose a Framework
Pick one to three frameworks from analytical-frameworks.md based on the question type.
Typical pairings:
- Current-state assessment -> gap analysis, architecture assessment
- Root cause -> 5 Whys, fishbone, causal analysis
- Comparison -> weighted scoring, MCDA
- Strategy -> SWOT, Porter's Five Forces, JTBD
- Technical assessment -> architecture review, technical debt assessment
3. Plan the Investigation
Break the work into MECE dimensions.
For each dimension, define:
- What evidence is needed
- Where it will come from
- What would confirm or contradict the current hypothesis
4. Collect Evidence
Use the minimum set of relevant sources:
- Repository files and docs
- Structured data or metrics
- Targeted commands
- Web research when current external information is required
Track evidence quality and note assumptions.
5. Analyze
Rules:
- Lead with evidence, not opinion
- Consider at least one alternative explanation
- State confidence explicitly
- Separate facts, inference, and recommendation
6. Present the Result
Use output-templates.md to structure the output.
All outputs should include:
- Executive summary
- Context
- Analysis
- Findings
- Recommendations
- Risks and limitations
Companion Resources
analytical-frameworks.mdoutput-templates.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

