mcpbeat Sign in

Thinking Circle Of Competence Agent Skill

Use when a specific claim may lack grounding. Check evidence boundary, size wrongness cost, then answer, fetch, or abstain — never confabulate.

735 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
928
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-circle-of-competence

The instruction itself

6 sections, as written by the author

Circle of Competence

Treat competence as an evidence boundary, not self-image. Answer only when grounded; otherwise fetch, mark uncertainty, or abstain. The failure mode is a fluent fabrication treated as fact.

When to Use

  • About to assert a specific fact (API, path, number, config, version behavior) without a citable source from this session.
  • The claim is about this codebase or system and you have not read or run the relevant artifact.
  • Pattern reconstruction would sound complete but is unconfirmed.
  • Cost of a wrong confident answer is material (security, data, irreversible action, trust).

When NOT to Use

  • Claim is grounded in something you read, ran, or can cite this session, or is stable universal knowledge — answer without false humility.
  • Error cost is trivial and reversible and you will flag the claim as unverified.
  • Grounding is one cheap fetch away — fetch first; abstention is not an excuse to skip a check.
  • User explicitly wants labeled brainstorming or hypotheticals.

Procedure

  • Name the claim. Isolate the assertion that would be treated as fact.
  • Classify the zone.
  • *Grounded:* citeable session source (read/run) or stable non-version-specific knowledge.
  • *Partial:* general shape known; version/repo/config detail unconfirmed.
  • *Ungrounded:* would invent a concrete value with no source.
  • Size wrongness cost. If high-stakes (security, data loss, irreversible ops), treat Partial as Ungrounded until verified.
  • Act by zone.
  • Grounded → answer; cite when useful; do not hedge verified facts.
  • Partial → cheap fetch then answer; else answer only with explicit uncertainty and a check path.
  • Ungrounded → fetch if possible; else ask or abstain with what would enable an answer. Never invent.
  • Refuse competence creep. Adjacent code, prior versions, or general capability do not ground the unread target.
  • Stop. Emit answer, fetch request, or abstention. Do not round "probably" to a flat assertion.

Stop condition: Claim answered with grounding, marked partial with a check path, or refused with missing-evidence note.

Output

Claim: <assertion>
Zone: grounded | partial | ungrounded
Evidence: <source or none>
Wrongness cost: low | medium | high
Action: answer | fetch-then-answer | answer-with-uncertainty | abstain/ask
Response: <wording or missing artifact>

Verification

  • Falsify if a specific value was asserted with no session source and no uncertainty marker.
  • Falsify if Partial/high-stakes was treated as Grounded, or a cheap fetch was skipped for abstention theater.
  • Over-application guard: do not hedge or refuse claims verified this session.

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take tjboudreaux/thinking-circle-of-competence from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.