Individual skill

domain

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.

plugins/boshu2/agentops/skills/domain/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,532
Repository last updated: Nov 6, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-coding Repository topic
awesome Repository topic
awesome-list Repository topic
codex Repository topic
codex-plugins Repository topic
openai Repository topic
codex-skill Repository topic
codex-skills Repository topic
marketplace Repository topic
codex-marketplace Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,212 bytes
references/agentops-terms.mddoc · 835 bytes
references/caller-vocabulary.mddoc · 2,289 bytes
references/standards/common-standards.mddoc · 19,332 bytes
references/standards/go.mddoc · 20,006 bytes
references/standards/javascript.mddoc · 2,112 bytes
references/standards/json.mddoc · 1,147 bytes
references/standards/llm-trust-boundary-checklist.mddoc · 2,384 bytes
references/standards/markdown.mddoc · 879 bytes
references/standards/python.mddoc · 7,968 bytes
references/standards/race-condition-checklist.mddoc · 3,355 bytes
references/standards/rust.mddoc · 2,451 bytes
references/standards/shell.mddoc · 838 bytes
references/standards/skill-structure.mddoc · 6,717 bytes
references/standards/sql-safety-checklist.mddoc · 2,902 bytes
references/standards/test-pyramid.mddoc · 4,474 bytes
references/standards/typescript.mddoc · 1,112 bytes
references/standards/yaml.mddoc · 1,504 bytes
scripts/validate.shruns · 2,457 bytes

Read excerpt

# Domain

Two independent uses: [vocabulary work](#vocabulary-work) makes a term, name or
rule boundary precise enough for acceptance examples, code and conversation; a
[standards lookup](#standards-lookup) finds the language, data-format, risk or
test-design standard for a change. Neither needs the other. [Plan](../plan/SKILL.md)
owns unified discovery and resumption; Domain resolves only the needed
vocabulary or rule boundary and returns it to the existing intent.

## Vocabulary work

1. **Cite the existing owner.** Find the vocabulary owner in the caller's
   instructions, domain docs or contracts and read only the relevant terms. A
   lookup is read-only. With no owner, label each definition as observed in
   code or proposed.