agentleFS
Sign inStart free
qimen039-codeqimen039-code/agent-cognitive-continuity-framework/skills/shared-semantic-anchors/SKILL.md

shared-semantic-anchors

Skill2 starsChanged 28 days agoMITView on GitHub

Use when a user explicitly defines or corrects reusable project terminology. Store confirmed meaning and boundaries in the adopting workspace, with authorization for durable writes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. qimen039-code/claim-boundary-harness★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only anchor semantics the user explicitly defines or corrects.

    line 12
  2. Distinctive:

    Do not store assistant guesses as anchors.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Shared Semantic Anchors

This file starts empty by design. It is not a glossary and not a fact database.

Rules

  1. Only anchor semantics the user explicitly defines or corrects.
  2. Store both meaning and non-meaning.
  3. Preserve exact phrase boundaries.
  4. Do not store assistant guesses as anchors.
  5. Route troubleshooting-related anchors through the troubleshooting skill matrix when needed.

Anchor Index

Anchor IDPhraseUse when
ANCHOR-EXAMPLEexample phraseReplace after adoption.

Anchor Template

## ANCHOR-EXAMPLE

phrase:
exact_trigger:
anchored_meaning:
non_meaning:
applicable_boundaries:
non_applicable_boundaries:
source:
update_rule:
related_points:

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