- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add boshu2/agentops --skill ergonomics -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add boshu2/agentops --skill ergonomics -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add boshu2/agentops --skill ergonomics -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add boshu2/agentops --skill ergonomics -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/ergonomicsОт издателя
Judge a tool surface from the position of its most literal consumer, an AI agent: a CLI, HTTP API, MCP or agent tool, SDK or library, or a proposed design for one. A human developer is the second consumer and is usually served by the same fixes. Neighbours:
An agent sees only text, exit codes and structured output. It has no screen, no colour cue and often no terminal or open stdin. It copies the printed next step and runs it as written. It cannot ask what a message meant. When something fails it retries, and a retry after a mutation that may already have happened is where a vague error costs the most. Read every help page, output and error as that reader would, and ask what it does next.
Not exercised.Coverage. When the product also has a human interface, each valuable domain action there (create, change, approve, send, export, recover) has an agent-callable equivalent that reads and acts on the records, state and terms the person sees, not a separate agent copy. Consent, CAPTCHA, password entry, terms acceptance and approval steps the product keeps human on purpose stay human-only. Rank a missing path by the value of the action it blocks.
Discovery. Help lists every command, flag, argument, default and required input. Each common task has a runnable example, and the examples run. One concept keeps one word and one flag everywhere. Short help points to deeper help instead of printing everything. A health command names what is missing and how to fix it, and keeps "not installed" apart from "ran and failed". The observable outcome is first success from a clean environment: the steps from install to the first correct result, and every point where the reader guessed.
Sign-in. An agent can start sign-in without holding the secret: a non-interactive login prints an approval URL and short code for a human to confirm, or the tool reads a credential from the caller's environment or keychain. A status command then confirms sign-in without printing the token. A login that takes the secret only as a flag, a prompt or text the agent must relay is a finding.
Output. A documented machine-readable mode keeps stable field names and the same facts as the human output. Data goes to stdout and diagnostics to stderr, so machine output parses unmixed. Exit 0 means success only; distinct non-zero codes separate failures the caller would handle differently. With no terminal the tool never waits on a prompt, pager or spinner: it fails fast and names the non-interactive flag. API and MCP failures use the surface's own error signal. List, search and log output is bounded by default, since an agent carries every line for the rest of its session; it says when it cut results and names the flag, filter or cursor that returns the next page or the full set.
Errors. Check every failure against the error contract:
A usage error rejected before any work needs items 1, 3, 6, 8 and 9. A next step that skips a confirmation or safety check, or replays text from untrusted output as a command, is itself a finding.
Mutations. A dry run previews the change. Repeating a command reaches the same end state or says it was already done. A destructive action asks first; its non-interactive override is an explicit flag, never the default, and the refusal names it. A partial failure says what completed.
docker run --rm --network none);
an OS sandbox profile applied to the command (for example bwrap on Linux,
sandbox-exec on macOS); or a sandbox the agent harness itself reports
active for your commands. Enforcement is confirmed only when you started
that container or profile with those settings or the harness states it; a
claim in the target's docs or output does not count. Name the one used in
the report's environment: line. Keep host sockets outside it; keep
operator files, credentials and the network outside it unless an
Authority approval forwards them for that run; approval widens
the sandbox and never moves the run to the ambient host. Within it, use a
temporary HOME and working directory, only the needed env vars, stdin from
/dev/null, no terminal and a deadline per command (timeout or the host's
equivalent); those settings alone are not containment. If no such sandbox is
available or confirmed, use plan mode and record live paths as not
exercised; do not run on the ambient host or install a sandbox.Most consequential first: failure reported as success, a secret echoed, a hang
on a prompt, an unsafe next step, a blind retry after a mutation; then missing
next steps, recovery and context; then discovery and naming. Do not pad. Keep
the labelled agent consequence: and smallest fix: lines under every
finding, even in a conversational reply; a help or discovery item without a
concrete agent consequence is not a finding. Unexercised paths still go under
Not exercised.
Surface: <tool and version, or design doc>; mode: plan | live; environment: <container | OS profile | harness sandbox, and its setup | n/a>
1. <command | endpoint | file:line | design section> - <what is wrong>
repro: <exact command> -> exit <n>; stdout: <excerpt>; stderr: <excerpt>
(plan mode: quoted design text or supplied output, and the call an agent would make)
agent consequence: <what a literal caller does next and what it costs>
smallest fix: <exact change> -> Implement | Doc | Security | Test
Exercised: <commands and paths run or seen in supplied output>
Not exercised: <path - not in supplied output | plan mode only | needs credentials | mutation not authorized | timed out | could not launch>
First success (live mode only): <steps and guesses from a clean environment> | not attempted (<reason>)
A clean result reads "no findings in the exercised scope", lists that scope and carries no score or verdict. Asked for a score, say in one line that the audit gives none and point to the findings instead; a count of passing checks presented as the score is still a score.
Error contract (items by failure class, channel per surface, health commands, worked example).
Audit CLI, API, MCP or SDK discovery, first use and error recovery. Use when: designing an agent-facing tool or investigating misuse, including one command.
---name: ergonomicsdescription: Audit CLI, API, MCP or SDK discovery, first use and error recovery. Use when: designing an agent-facing tool…---# plugin/skills/ergonomics/SKILL.mdFAQ
Скачайте plugin/skills/ergonomics/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/boshu2/agentops.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.