agentleFS
charleslucascharleslucas/poe_mcp_suite/.claude/skills/knowledge-frameworks/SKILL.md

knowledge-frameworks

Skill9 starsChanged 3 months agoMITView on GitHub

Maintain the shared knowledge frameworks in frameworks/ — style templates (archetype rosters), the cross-build tech/concepts database, and the farming strategy roster. Use for "add X to the minions template", "survey how people farm currency", "record this tech", "re-stamp farming tiers for the new league", or standing up a new framework (totems, melee, ...). Runs surveys through the existence/obtainability gates and confidence labels.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Read playbooks/README.md first — the shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy, narration norms).

    line 9

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

This task uses the Knowledge Frameworks playbook. The playbooks in playbooks/ are the single source of truth — read them rather than working from memory.

  1. Read playbooks/README.md first — the shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy, narration norms).
  2. Then read playbooks/knowledge-frameworks.md and follow it.

Key points:

  • Frameworks live in frameworks/ (committed, public); character/archetype instances stay in the private guide library.
  • Gate every survey claim: existence (fuzzy-grep names!), obtainability, mechanics_index scope.
  • Label everything ✅/◐/⛔ and keep ⛔ rows with reasons; record aliases and references as encountered.
  • Ledger every survey with date, queries, and source quality.

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.