agentleFS
vanzan01vanzan01/claude-agent-sdk-starter/.claude/skills/analysis-helper/SKILL.md

analysis-helper

Skill9 starsChanged 10 months agoMITView on GitHub

Format instructions for news analysis output.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    NO JSON - do not output curly braces {} or square brackets []

    line 44
  2. Distinctive:

    NO markdown - do not use \*\* or ## or ` or \_

    line 45
  3. Distinctive:

    NO code blocks - do not wrap output in ```

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Analysis Helper

CRITICAL: Output Format

You receive JSON input, but you MUST output PLAIN TEXT (not JSON).

Your output MUST look EXACTLY like this:

Winner: [copy the exact title from input]
Why it matters: [2-3 sentences explaining significance]

WRONG vs CORRECT

WRONG - JSON output (DO NOT DO THIS):

{ "winner": { "title": "...", "why_it_matters": "..." } }

WRONG - Markdown:

**Winner:** Some headline

CORRECT - Plain text only:

Winner: OpenAI releases GPT-5
Why it matters: This is significant because it represents a major leap in AI capabilities.

Rules

  1. Output starts with Winner: (plain text, no asterisks)
  2. Then Why it matters: (plain text, no asterisks)
  3. NO JSON - do not output curly braces {} or square brackets []
  4. NO markdown - do not use ** or ## or ` or _
  5. NO code blocks - do not wrap output in ```
  6. Just two lines of plain text

BEFORE YOU OUTPUT - CHECK:

❌ Does my output contain { or } or [ or ]? → REMOVE THEM ❌ Does my output contain ** or ## or ``? → REMOVE THEM ❌ Does my output start with anything other than "Winner:"? → FIX IT ❌ Is my output wrapped in code blocks ```? → REMOVE THE BLOCKS ✅ Is it EXACTLY: "Winner: [title]\nWhy it matters: [explanation]"? → GOOD!

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.