Compile Knowledge
sickn33/agentic-awesome-skills
Compile durable, non-obvious findings into an interlinked markdown knowledge store — atomic files, [[wiki-links]], a maintained index — so an agent gets smarter across sessions instead of relearning…
Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors.
Apache-2.0Auto-check passed
Install Build For Testing
$ npx skills add adamayoung/TMDb --skill build-for-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install adamayoung/TMDb build-for-testing --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/adamayoung/TMDb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/build-for-testing .claude/skills/build-for-testing && 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 "build-for-testing" agent skill from https://github.com/adamayoung/TMDb/tree/main/.claude/skills/build-for-testing into .claude/skills/build-for-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-for-testing", 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/adamayoung/TMDb/tree/main/.claude/skills/build-for-testingType 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 adamayoung/TMDb --skill build-for-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install adamayoung/TMDb build-for-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamayoung/TMDb.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/build-for-testing .agents/skills/build-for-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-for-testing" agent skill from https://github.com/adamayoung/TMDb/tree/main/.claude/skills/build-for-testing into .agents/skills/build-for-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-for-testing", 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 adamayoung/TMDb --skill build-for-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install adamayoung/TMDb build-for-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamayoung/TMDb.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/build-for-testing .cursor/skills/build-for-testing && 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 "build-for-testing" agent skill from https://github.com/adamayoung/TMDb/tree/main/.claude/skills/build-for-testing into .cursor/skills/build-for-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-for-testing", 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/adamayoung/TMDb.git --path .claude/skills/build-for-testing--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 adamayoung/TMDb --skill build-for-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install adamayoung/TMDb build-for-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamayoung/TMDb.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/build-for-testing .gemini/skills/build-for-testing && 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 "build-for-testing" agent skill from https://github.com/adamayoung/TMDb/tree/main/.claude/skills/build-for-testing into .gemini/skills/build-for-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-for-testing", 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 adamayoung/TMDb build-for-testingInstalls 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 adamayoung/TMDb --skill build-for-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/adamayoung/TMDb.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/build-for-testing .github/skills/build-for-testing && 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 "build-for-testing" agent skill from https://github.com/adamayoung/TMDb/tree/main/.claude/skills/build-for-testing into .github/skills/build-for-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-for-testing", 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 adamayoung/TMDb --skill build-for-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install adamayoung/TMDb build-for-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamayoung/TMDb.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/build-for-testing .opencode/skills/build-for-testing && 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 "build-for-testing" agent skill from https://github.com/adamayoung/TMDb/tree/main/.claude/skills/build-for-testing into .opencode/skills/build-for-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-for-testing", 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
build-for-testing- GitHub stars
- 178
- Token cost
- ~608 tokens
- SKILL.md length
- 289 words
- Files
- 1
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors.
- Calls make
What it does
Build For Testing is an agent skill from adamayoung/TMDb. Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors. Use after changing tests or shared code to check everything still builds — delegates to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary. Differs from /build, which compiles only the library; to run the tests, use /test.
Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: The Movie Database Swift Package. The licence is Apache-2.0.
Example prompts
- “/build-for-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit a3f1311. 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
Shell commands in SKILL.md call:
make
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
Build For Testing loads about 608 tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 289 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
The full file from adamayoung/TMDb at commit a3f1311, republished under its Apache-2.0 licence (© adamayoung). 289 words, ~608 tokens.
Download SKILL.mdSave it as
.claude/skills/build-for-testing/SKILL.md (or your agent's skills folder).- name
- build-for-testing
- description
- Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors. Use after changing tests or shared code to check everything still builds — delegates to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary. Differs from /build, which compiles only the library; to run the tests, use /test.
Build for testing
Spawn the tooling-runner agent (Agent tool,
subagent_type: tooling-runner — its Haiku pin, command recipes, and
reporting contract live in .claude/agents/tooling-runner.md) with the
one-line task:
Run the
build-for-testingtarget: compile the TMDb package and all test targets. Package directory:<your current working directory, absolute>
Always include that directory line. The subagent does not reliably inherit
your working directory, and without it a run inside a git worktree silently
builds the main checkout instead (see .claude/agents/tooling-runner.md).
Use your actual CWD — run pwd if you are not certain of it.
Relay its report. Do not run the build yourself — unless the report is missing or malformed (below), which is the only sanctioned fallback.
If the report is unclear on a failure, read the log path it reports
(.build/last-build-tests.log) — or, inside Xcode, refresh diagnostics on
the flagged files — rather than re-running. After fixing the issues,
re-invoke this skill to re-check (a fresh subagent will rebuild).
If the report is missing or malformed
Judge the runner's report by shape, not by tone — the three outcomes are distinguishable and must be handled differently:
| Report | What it means | What you do |
|---|---|---|
Status: refused — … | A caller bug (wrong/missing package directory) | Surface it as a hard error and fix the call. Never fall back — the runner is telling you your invocation was unsafe. |
Status: passed/failed | A real result | Relay it; act on any failures |
No report, empty, or missing the Directory:/Status: lines | The subagent died — the run is void, not failed | Re-invoke once. If it voids again, run make -C "<the same absolute directory you passed the runner>" build-tests directly via Bash |
A fallback run is disclosed in your summary — say that you fell back and why. It is never silently treated as an ordinary result.
© adamayoung, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/build-for-testing of adamayoung/TMDb.
Open the folder on GitHubat commit a3f1311
Compare with similar skills
Build For Testing 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 |
|---|---|---|---|---|---|---|
| Build For Testing this skilladamayoung/TMDb | 178 | — | ~608 | Automated safety check: Pass | Apache-2.0 | |
| Compile Knowledgesickn33/agentic-awesome-skills | 47k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Compileratopile/atopile | 4k | — | ~1k | Automated safety check: Pass | MIT | |
| Touch Targetsthedaviddias/Front-End-Checklist | 74k | — | ~938 | Automated safety check: Pass | MIT | |
| Tmdbsundial-org/awesome-openclaw-skills | 663 | — | ~829 | Automated safety check: Pass | None | |
| Paddle Design CompilerPaddlePaddle/Paddle | 24k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Compiler
atopile/atopile
How the atopile compiler builds and links TypeGraphs from .ato (ANTLR front-end → AST → TypeGraph → Linker → DeferredExecutor), plus the key invariants and test entrypoints.
Touch Targets
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to all interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items.
Tmdb
sundial-org/awesome-openclaw-skills
Search movies/TV, get cast, ratings, streaming info, and personalized recommendations via TMDb API.
Paddle Design Compiler
PaddlePaddle/Paddle
A skill your agent uses when working with Paddle 3.0 compiler full pipeline: SOT (Symbolic Opcode Translator) for bytecode-level dy2st graph capture, PIR (Paddle IR) for SSA-based intermediate…
Compile
ccplugins/awesome-claude-code-plugins
Compile an Anthropic-style skill — a directory with a SKILL.md and optional references/ — into a deterministic, runnable workflow via the rote CLI.
More from adamayoung/TMDb
All 18 skills in this repoSwift DocC Documentation
adamayoung/TMDb
Writes and maintains DocC /// comments for the public API of the TMDb Swift package, following the project's summary patterns and comment structure.
TMDb Integration Failure Fixer
adamayoung/TMDb
Diagnoses a failing scheduled TMDb Integration run, re-runs transient failures, and fixes real API drift on its own branch with a PR, merging it only when told to.
Implement Plan (Canon TDD)
adamayoung/TMDb
Drives an approved plan to completion test-first, deriving a Canon TDD test list, showing it before any code and stopping only when every item is written, passing and green.
TMDb Backlog Triager
adamayoung/TMDb
Grooms the Backlog column of a GitHub project board by re-verifying each issue against current main, closing dead ones, promoting actionable ones to Ready and naming the decision the rest need.
Canon TDD Workflow
adamayoung/TMDb
Has your agent build features and fix bugs in Canon TDD order: write a test list, then one failing test, make it pass, refactor, and repeat until the list is empty.
Capture Knowledge
adamayoung/TMDb
Records non-obvious lessons from a finished task, such as gotchas, API quirks and design decisions, into a project's knowledge folder before a pull request opens.
Questions about Build For Testing
What does Build For Testing do?
Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors. Build For Testing is an agent skill from adamayoung/TMDb. Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors.
How do I install Build For Testing in Claude Code?
Run `npx skills add adamayoung/TMDb --skill build-for-testing -a claude-code`. Or copy the skill folder (.claude/skills/build-for-testing in adamayoung/TMDb) into .claude/skills/build-for-testing in your project. Claude Code loads it when a task matches its description.
How do I install Build For Testing in Codex?
Run `npx skills add adamayoung/TMDb --skill build-for-testing -a codex`. Or copy the skill folder (.claude/skills/build-for-testing in adamayoung/TMDb) into .agents/skills/build-for-testing in your project. Codex loads it when a task matches its description.
Can I use Build For Testing 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 adamayoung/TMDb --skill build-for-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-for-testing, .gemini/skills/build-for-testing, .github/skills/build-for-testing and .opencode/skills/build-for-testing in your project.
What does Build For Testing need to run?
Going by SKILL.md and its folder, Build For Testing needs the command-line tools its instructions call (make).
Does Build For Testing 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 Build For Testing 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 Build For Testing use?
Build For Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Build For Testing use?
About 608 tokens (SKILL.md is roughly 2.4k 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 Build For Testing?
Skills that share tags, products or a category with Build For Testing: Compile Knowledge (sickn33/agentic-awesome-skills, 47k stars), Compiler (atopile/atopile, 4k stars), Touch Targets (thedaviddias/Front-End-Checklist, 74k stars) and Tmdb (sundial-org/awesome-openclaw-skills, 663 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Build For Testing?
adamayoung (a GitHub user) maintains it in adamayoung/TMDb, which has 178 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 3, 2026.
Source: adamayoung/TMDb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.