agentleFS
Sign inStart free
ExarLabsExarLabs/paros-advisor/skills/think/SKILL.md

think

Skill4 starsChanged 41 days agoMITView on GitHub

Orchestrate several AIs on one question in a PAROS vault: assemble a team with roles (researcher, strategist, validator), send fat prompts with a findings contract in parallel over API or browser, merge the answers, and keep a brainstorm state file. Use when the person asks to "think this through with several AIs", "brainstorm", "research from several angles", "attack this plan", or shares an AI conversation link to bring into the vault.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use hunt, read and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ninehillsSkill

    hunt

    Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

    Also in 5 projects that use this

  • MicrosoftSkill

    read

    Read pages from a document. Returns MinerU markdown (preferred) or PyPDF text, with optional page screenshots and sub-image fetching. When markdown is available, a figure_images_meta catalog is included — use the figures parameter to fetch specific sub-image pixels. Triggers include "read page 5", "what does page 12 say", "show me the chart on page 3", "extract pages 3-5".

    Also in 6 projects that use this

  • DockerSkill

    write

    Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

    Also in 7 projects that use this

  • genomewalkerSkill

    health

    Soul system health check with remediation

    Also in 5 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 6 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Read it in full. Read its version: field.

    line 14
  2. Very specific:

    Follow it. Its ## Constitution always wins.

    line 18
  3. Very specific:

    If the person corrects the result, write a learning packet to the skill's observations/ folder (P05).

    line 19

“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “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

think

Thin entry (PAROS P04). The knowledge lives in a live definition; this file only finds it.

  1. Locate the live definition, first match wins:
    • where the vault entry file (AGENTS.md or CLAUDE.md) says skills live: <skills folder>/think/CURRENT.md;
    • <vault>/PAROS/skills/think/CURRENT.md;
    • the PAROS reference copy: <paros repo>/skills/think/CURRENT.md.
  2. Read it in full. Read its version: field. Then read LOCAL.md next to it (personal setup); if missing, offer to create it from LOCAL.example.md.
  3. Report one line before working:
    • from the vault: Running think v<X> from your vault;
    • from the reference copy: Running think v<X> from the PAROS reference, not yet adopted.
  4. Follow it. Its ## Constitution always wins.
  5. If the person corrects the result, write a learning packet to the skill's observations/ folder (P05).

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