agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/problem-structuring/SKILL.md

problem-structuring

Skill114 starsChanged 10 months agoMITView on GitHub

Break down complex problems into actionable recommendations using deductive and inductive analysis.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When facing a complex, ambiguous problem that needs structured analysis.

    line 12
  2. Distinctive:

    Start broad, work to specifics:

    line 24
  3. Distinctive:

    Create logical tree of options

    line 26
  4. Distinctive:

    Start with specifics, find patterns:

    line 32
  5. Distinctive:

    Look for patterns and trends

    line 34
  6. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Problem Structuring

Break down complex problems into actionable recommendations.

When to Use

When facing a complex, ambiguous problem that needs structured analysis.

The Process

1. Simplify the Problem

  • Identify core components
  • List key stakeholders
  • Summarize in 2-3 sentences

2. Deductive Analysis (Top-Down)

Start broad, work to specifics:

  • What's the general situation?
  • Create logical tree of options
  • Map cause-and-effect relationships
  • Explore branches and outcomes

3. Inductive Analysis (Bottom-Up)

Start with specifics, find patterns:

  • Examine data points and examples
  • Look for patterns and trends
  • What do specifics suggest about the whole?

4. Synthesize

Combine both approaches:

  • Where do they agree?
  • Where do they conflict?
  • What insights emerge?

5. Develop Recommendation

Based on analysis:

  • Clear, actionable recommendation
  • Rationale tied to analysis
  • Trade-offs acknowledged

Output Format

  • Simplified problem: Concise summary
  • Deductive analysis: Logical tree with options
  • Inductive analysis: Patterns from data
  • Synthesis: Combined insights
  • Recommendation: Clear action with rationale

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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.

Check your setup, free