- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add boshu2/agentops --skill domain -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add boshu2/agentops --skill domain -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add boshu2/agentops --skill domain -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add boshu2/agentops --skill domain -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/domain게시자 제공
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.mdFAQ
게시자에게서 plugin/skills/domain/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/boshu2/agentops에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.