Nlm Skill
iusztinpaul/ai-research-os-workshop
Expert guide for the NotebookLM CLI (nlm) and MCP server - interfaces for Google NotebookLM.
How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives…
Install Checks
$ npx skills add OtoDock/oto-dock --skill checks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OtoDock/oto-dock checks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/mcps/custom/checks-mcp/skills/checks .claude/skills/checks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "checks" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checks into .claude/skills/checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OtoDock/oto-dock --skill checks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OtoDock/oto-dock checks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .agents/skills && cp -r skills-src/mcps/custom/checks-mcp/skills/checks .agents/skills/checks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "checks" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checks into .agents/skills/checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OtoDock/oto-dock --skill checks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OtoDock/oto-dock checks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/mcps/custom/checks-mcp/skills/checks .cursor/skills/checks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "checks" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checks into .cursor/skills/checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OtoDock/oto-dock.git --path mcps/custom/checks-mcp/skills/checks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OtoDock/oto-dock --skill checks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OtoDock/oto-dock checks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/mcps/custom/checks-mcp/skills/checks .gemini/skills/checks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "checks" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checks into .gemini/skills/checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OtoDock/oto-dock checksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OtoDock/oto-dock --skill checks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .github/skills && cp -r skills-src/mcps/custom/checks-mcp/skills/checks .github/skills/checks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "checks" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checks into .github/skills/checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OtoDock/oto-dock --skill checks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OtoDock/oto-dock checks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/mcps/custom/checks-mcp/skills/checks .opencode/skills/checks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "checks" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/checks-mcp/skills/checks into .opencode/skills/checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
checks- GitHub stars
- 190
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,144 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives…
- Explaining a check
- SKILL.md covers The four kinds, The document, Where checks live, who does what and Writing a rubric that helps, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A checks findings arrive in a session
What it does
Checks is an agent skill from OtoDock/oto-dock. How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives and who may create, attach or remove one, how to write a rubric that yields located findings, and the tools of the checks MCP. Use when creating, attaching, editing or explaining a check, or when a check's findings arrive in a session.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Education, covering Quizzes and assessments and MCP servers. It works with Model Context Protocol. The repository describes itself as: The agentic company OS. The brains of your company, built on Claude Code and Codex, working on your Anthropic and OpenAI subscriptions.
When your agent uses it
- Explaining a check
- A checks findings arrive in a session
Example prompts
- “/checks”
What it can do on your machine
Read from SKILL.md and the folder at commit 5308f5a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Checks loads about 2.2k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 1,144 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,144 words (~2,207 tokens).
“A check is a named, reusable unit that judges work. It runs at the end of a turn — a chat's, a task run's, a delegation's — looks at what the turn changed and answered, and either lets the turn…”
- name
- checks
Files
Just SKILL.md in mcps/custom/checks-mcp/skills/checks of OtoDock/oto-dock.
Open the folder on GitHubat commit 5308f5a
Compare with similar skills
Checks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Checks this skillOtoDock/oto-dock | 190 | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Nlm Skilliusztinpaul/ai-research-os-workshop | 179 | 1 repos | ~6.9k | Automated safety check: Pass | MIT | |
| MCPA Certification Tutorrohitg00/ai-engineering-from-scratch | 66k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Learn MCP Tutorrohitg00/ai-engineering-from-scratch | 66k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Vulnerability Triageprovos/ironcurtain | 613 | — | ~6.3k | Automated safety check: Pass | Apache-2.0 | |
| Flutter MCP Toolkit Dogfood IterationsArenukvern/mcp_flutter | 386 | — | ~919 | Automated safety check: Pass | MIT |
Similar skills
MCPA Certification Tutor
rohitg00/ai-engineering-from-scratch
Turns a GitHub course repository into an interactive tutor for the MCP Associate certification, making the learner explain and defend each step.
Learn MCP Tutor
rohitg00/ai-engineering-from-scratch
An interactive tutor for the Model Context Protocol path in AI Engineering from Scratch, teaching one lesson per invocation and recording wire evidence in MCP-LEARNING.md.
Vulnerability Triage
provos/ironcurtain
Reference vocabulary for interpreting vulnerability findings — detector-vs-impact distinction, severity anchoring on demonstrated evidence, the eleven-item interpretation rubric, delegation…
Flutter MCP Toolkit Dogfood Iterations
Arenukvern/mcp_flutter
Runs and records showcase/fluttertestapp dogfood iterations (toolqualityrubric, rundogfoodeval.sh, dogfoodwebeval.yaml).
Siyuan MCP Tag Flashcard
yangtaihong59/siyuan-plugins-mcp-sisyphus
MCP playbook for SiYuan tags and flashcards. An agent skill from yangtaihong59/siyuan-plugins-mcp-sisyphus.
More from OtoDock/oto-dock
All 19 skills in this repoAgent Creation
OtoDock/oto-dock
How to author an agent template folder and install it as a new agent - folder layout, manifest fields, persona rules, shipped apps and checks, and the scaffold-validate-create flow.
Image Search Usage
OtoDock/oto-dock
Search the web for images with filters and download them. An agent skill from OtoDock/oto-dock.
Subtitle Burning
OtoDock/oto-dock
Transcribe audio and burn styled subtitles into videos. An agent skill from OtoDock/oto-dock.
Triggers Guide
OtoDock/oto-dock
Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…
MCP Authoring
OtoDock/oto-dock
Author an MCP package for OtoDock: the manifest.json fields and their rules, the package layout, what the installer refuses or drops, credentials and instances, skills bundled with an MCP, and the…
Otodock Platform
OtoDock/oto-dock
How the OtoDock platform itself works and where every setting lives — installing and first-run setup, agents, AI engines, sessions, apps and sharing, checks, departments and delegation, shared…
Related
Works with
Categories
Questions about Checks
What does Checks do?
How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives…. Checks is an agent skill from OtoDock/oto-dock. How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives and who may create, attach or remove one, how to write a rubric that yields located findings, and the tools of the checks MCP.
When should I use Checks?
Checks fits situations like: explaining a check; A checks findings arrive in a session.
How do I install Checks in Claude Code?
Run `npx skills add OtoDock/oto-dock --skill checks -a claude-code`. Or copy the skill folder (mcps/custom/checks-mcp/skills/checks in OtoDock/oto-dock) into .claude/skills/checks in your project. Claude Code loads it when a task matches its description.
How do I install Checks in Codex?
Run `npx skills add OtoDock/oto-dock --skill checks -a codex`. Or copy the skill folder (mcps/custom/checks-mcp/skills/checks in OtoDock/oto-dock) into .agents/skills/checks in your project. Codex loads it when a task matches its description.
Can I use Checks in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OtoDock/oto-dock --skill checks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/checks, .gemini/skills/checks, .github/skills/checks and .opencode/skills/checks in your project.
What does Checks need to run?
SKILL.md names no scripts, command-line tools or credentials: Checks is instructions for the agent only.
Does Checks access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Checks safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Checks use?
Checks has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Checks use?
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Checks?
Skills that share tags, products or a category with Checks: Nlm Skill (iusztinpaul/ai-research-os-workshop, 179 stars), MCPA Certification Tutor (rohitg00/ai-engineering-from-scratch, 66k stars), Learn MCP Tutor (rohitg00/ai-engineering-from-scratch, 66k stars) and Vulnerability Triage (provos/ironcurtain, 613 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Checks?
OtoDock (a GitHub organization) maintains it in OtoDock/oto-dock, which has 190 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: OtoDock/oto-dock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.