agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/analyze/SKILL.md

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

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.
  • ArvorCoSkill

    constitution

    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-FoundrySkill

    revise

    Revise an existing spec based on feedback or correction

    Also in 3 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    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

  • DockerSkill

    write

    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

  • woosikkimSkill

    cancel

    Clear any stale OMC-Slim state

    Also in 3 projects that use this

  • +1 more from ArvorCo

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
  1. Distinctive:

    Read AGENTS.md at the project root to understand the project's domain, tech stack, and business context.

    line 14
  2. Distinctive:

    Use the minimum set of relevant sources:

    line 51
  3. Distinctive:

    Consider at least one alternative explanation

    line 65
  4. Very specific:

    Use output-templates.md to structure the output.

    line 71
  5. Distinctive:

    All outputs should include:

    line 73

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md
  • output-templates.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.