agentleFS
creanlabcreanlab/agent-genome-lab/.agents/skills/tama-community-summarizer/SKILL.md

tama-community-summarizer

Skill2 starsChanged 4 months agoMITView on GitHub

Summarize shared research pool for community insights

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After receiving packs in research-pool/incoming/ or when querying community data.

    line 12
  2. Very specific:

    Read all files in research-pool/incoming/.

    line 17
  3. Very specific:

    If integrated with frontend, provide community data via /api/community endpoint.

    line 50

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

TAMA Community Summarizer

Aggregates and summarizes research pool data for community intelligence.

When to Use

After receiving packs in research-pool/incoming/ or when querying community data.

Procedure

1. Collect Packs

Read all files in research-pool/incoming/.

2. Aggregate

Count by:

  • Failure family (which families are most common?)
  • Violated invariant (which rules are broken most?)
  • Repair operator (which fixes are most reusable?)
  • Stack tags (which stacks have most issues?)

3. Identify Patterns

  • Most common failure families → community anti-patterns
  • Most effective repair operators → community best practices
  • Transferability hotspots → universally applicable lessons

4. Generate Summary

Save to research-pool/summaries/SUMMARY-YYYYMMDD.json:

{
  "summary_date": "2026-03-18",
  "total_packs": 5,
  "total_genomes": 42,
  "top_families": [
    { "family": "verification-skipped-before-done", "count": 12 },
    { "family": "silent-fallback-introduced", "count": 9 }
  ],
  "top_repair_operators": [
    { "operator": "add-e2e-verification-step", "count": 8 }
  ],
  "transfer_recommendations": [...]
}

5. For Dashboard

If integrated with frontend, provide community data via /api/community endpoint.

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.