agentleFS
charleslucascharleslucas/poe_mcp_suite/.claude/skills/community-survey/SKILL.md

community-survey

Skill9 starsChanged 3 months agoMITView on GitHub

Community consensus / pitfall discovery for a PoE build archetype via Google AI Mode (Reddit/YouTube synthesis) — mistakes, weaknesses, and improvements that guides miss.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 — shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy).

    line 9
  2. Very specific:

    Read playbooks/community-survey.md and follow it for this task.

    line 10
  3. Distinctive:

    Run both standard queries (A: pitfalls, B: improvements) in parallel

    line 13

≈ “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 Community Survey playbook.

  1. Read playbooks/README.md first — shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy).
  2. Read playbooks/community-survey.md and follow it for this task.

Key points:

  • Run both standard queries (A: pitfalls, B: improvements) in parallel
  • Filter results before writing to build-plan.md: mechanically plausible, concrete, and genuinely new
  • Mark community-sourced numbers as unverified until cross-checked in PoB
  • This is cursory-scope by default — no approval gate needed unless results trigger a follow-up analysis

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.