mcpbeat

Domain

boshu2/domain

Load the AgentOps language and bounded-context contracts when a term needs precise meaning. Triggers: "define this domain term", "check the bounded context".

494 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
416
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/boshu2/agentops --skill domain

The instruction itself

2 sections, as written by the author

Domain — ubiquitous language

Use this read-only library when an AgentOps term or bounded-context boundary

needs precise meaning.

Returning the exact contract definition works because two contexts that read

the same source line cannot drift apart on a term; a paraphrase reintroduces

the ambiguity the lookup exists to remove.

Named failure mode — synonym smuggling: answering with a near-synonym

("close" for "verdict") that quietly imports lifecycle authority the term does

not carry.

Anti-pattern: defining a term from memory because the contract file is one

read away. Corrective: always cite the definition and its source path from the

live contract, even for terms you are sure about.

Procedure

  • Read docs/contracts/ubiquitous-language.md for the term.
  • Read docs/contracts/bounded-contexts.yaml only when ownership or a port

boundary matters.

  • Return the exact definition and source path.
  • Stop.

Do not invent synonyms that imply lifecycle authority. In particular, Plan,

Candidate, manifest, verdict, revision, strategy, and adapter are semantic

terms; queue, claim, lease, close, land, release, and delivery belong to caller

systems rather than AgentOps core state.

Vocabulary changes are normal source edits to the two contracts above. This

skill does not promote terms, mutate a knowledge index, or create continuation.

How to use it

Copy the folder

Take boshu2/domain 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.