- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill domain -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill domain -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill domain -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill domain -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/domainDel publicador
This skill makes a run cite where the project defines a term or convention before using, renaming or applying it, and keep one meaning per bounded context. A user sees it worked when each contested term comes back with its source path, its context and a concrete example that tells the meanings apart.
Two independent uses: vocabulary work makes a term, name or rule boundary precise enough for acceptance examples, code and conversation; a conventions lookup finds the standard the repository itself sets for a change. Neither needs the other. Plan owns unified discovery and resumption; Domain resolves only the needed vocabulary or rule boundary and returns it to the existing intent.
Return vocabulary work in this shape. Stop when every contested term has a row with a source and a distinguishing example, or an open question for the caller:
After the table, list the translations between contexts, each located code-versus-intent disagreement, the compatibility cost of any proposed rename, and the owner updated or the text proposed for it. See caller vocabulary examples.
The synonym smuggling failure substitutes a word that changes a term's authority: calling a verdict a closure quietly assigns a tracker transition to judgment. Keep the original term when a substitute would move responsibility.
Only when AgentOps itself is the subject, load its owners from AgentOps terms. Do not apply AgentOps vocabulary to an unrelated caller domain.
The standard for a change is the one the repository sets. Find its owners for
the touched paths: instruction files (AGENTS.md, CLAUDE.md, path-scoped
rules), formatter, linter and type-checker configuration, the CI workflow that
gates the change, and the existing code and tests in the same package. Cite
each convention by path. Configuration and CI that run outrank prose; where
two owners disagree, report the conflict rather than pick one. When the
repository states nothing for a question, say so and follow the surrounding
code; do not present a general language guide as the project's rule. A lookup
is read-only and creates no second approval or validation lane. It is done
when each convention question for the touched paths has a cited owner or the
answer "not stated".
Idea provenance: Matt Pocock's engineering skills (domain modeling), adapted for AgentOps.
Settle what domain terms mean per context, and which repository conventions or language standards (Go, Python) apply. Use when: names disagree or a rename is proposed.
---name: domaindescription: Settle what domain terms mean per context, and which repository conventions or language standards (Go, Python)…---# plugin/skills/domain/SKILL.mdPreguntas frecuentes
Descarga plugin/skills/domain/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/boshu2/agentops.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.