Boneyard
0xGF/boneyard
Use boneyard-js to add, configure, debug, or rebuild skeleton screens.
Phase 4 of building an Inkline component — write colocated cross-target tests.
No licenceAuto-check: notes
Install Test Component
$ npx skills add inkline/inkline --skill test-component -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inkline/inkline test-component --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/inkline/inkline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/test-component .claude/skills/test-component && 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 "test-component" agent skill from https://github.com/inkline/inkline/tree/main/.claude/skills/test-component into .claude/skills/test-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-component", 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/inkline/inkline/tree/main/.claude/skills/test-componentType 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 inkline/inkline --skill test-component -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inkline/inkline test-component --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inkline/inkline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/test-component .agents/skills/test-component && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-component" agent skill from https://github.com/inkline/inkline/tree/main/.claude/skills/test-component into .agents/skills/test-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-component", 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 inkline/inkline --skill test-component -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inkline/inkline test-component --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inkline/inkline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/test-component .cursor/skills/test-component && 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 "test-component" agent skill from https://github.com/inkline/inkline/tree/main/.claude/skills/test-component into .cursor/skills/test-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-component", 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/inkline/inkline.git --path .claude/skills/test-component--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 inkline/inkline --skill test-component -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inkline/inkline test-component --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inkline/inkline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/test-component .gemini/skills/test-component && 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 "test-component" agent skill from https://github.com/inkline/inkline/tree/main/.claude/skills/test-component into .gemini/skills/test-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-component", 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 inkline/inkline test-componentInstalls 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 inkline/inkline --skill test-component -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inkline/inkline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/test-component .github/skills/test-component && 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 "test-component" agent skill from https://github.com/inkline/inkline/tree/main/.claude/skills/test-component into .github/skills/test-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-component", 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 inkline/inkline --skill test-component -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inkline/inkline test-component --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inkline/inkline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/test-component .opencode/skills/test-component && 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 "test-component" agent skill from https://github.com/inkline/inkline/tree/main/.claude/skills/test-component into .opencode/skills/test-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-component", 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
test-component- GitHub stars
- 1.5k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 338 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- None found
At a glance
Phase 4 of building an Inkline component — write colocated cross-target tests.
- Works in 4 steps: The actual @inkline/test-utils exports —… → The exemplar tests:… → ui/components/src/components/angular-ssr-… → …
- Strengthening a components tests
- SKILL.md covers Read first, Headless test — the baseline…, Styled test — add composition,… and Coverage — exercise every branch, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Component is an agent skill from inkline/inkline. Phase 4 of building an Inkline component — write colocated cross-target tests. Assert compilation to all 7 targets, expected diagnostics, conformance, output composition/imports/bindings, snapshots, and real-DOM behavior via Angular SSR. Targets ~100% line+branch coverage. Use when adding or strengthening a component's tests.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Angular and React. The repository describes itself as: Inkline is the intuitive UI Components library that gives you a developer-friendly foundation for building high-quality, accessible, and customizable Vue.js 3 Design Systems.
When your agent uses it
- Strengthening a components tests
Example prompts
- “/test-component”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Grep, Glob
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- The actual @inkline/test-utils exports — tooling/test-utils/src/index.ts (the prose runScenarioAcrossTargets is gone). Available…
- The exemplar tests: button/headless/IButtonBase.ink.test.ts (simple) and input/styled/IInput.ink.test.ts (comprehensive + Angular SSR).
- ui/components/src/components/angular-ssr-helper.ts — mountStyledOnAngular(importMetaUrl, styledRel, headlessRels, props?).
- .../reference/primitives.md — the per-target lowering table and expected notices.
What it can do on your machine
Read from SKILL.md and the folder at commit f4da55a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGrepGlob
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 typescript).
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
Test Component loads about 1.6k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 338 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 338 words (~1,626 tokens).
“Tests are colocated as .ink.test.ts (Vitest), next to the source they cover: the headless test in headless/, the styled test in styled/. They run the real compiler in-memory via @inkline/test-utils and assert across all 7 targets, plus real-DOM behavior on…”
- name
- test-component
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob
- triggers
- test a component, add tests for the component, write component tests
Files
Just SKILL.md in .claude/skills/test-component of inkline/inkline.
Open the folder on GitHubat commit f4da55a
Compare with similar skills
Test Component 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 |
|---|---|---|---|---|---|---|
| Test Component this skillinkline/inkline | 1.5k | — | ~1.6k | Automated safety check: Notes | None | |
| Boneyard0xGF/boneyard | 7.5k | — | ~2.2k | Automated safety check: Notes | MIT | |
| Feature SyncNG-ZORRO/ng-zorro-antd | 9.2k | — | ~840 | Automated safety check: Pass | MIT | |
| Winui AppLanceMcCarthy/DevOpsExamples | 172 | 1 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Markstream Custom ComponentsSimon-He95/markstream-vue | 3k | — | ~955 | Automated safety check: Pass | MIT | |
| Screenmapaleqsio/screenmap | 242 | — | ~7.2k | Automated safety check: Pass | MIT |
Similar skills
Feature Sync
NG-ZORRO/ng-zorro-antd
Sync an Ant Design React component or feature into NG-ZORRO.
Winui App
LanceMcCarthy/DevOpsExamples
Bootstrap, develop, and design modern WinUI 3 desktop applications with C and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and…
Markstream Custom Components
Simon-He95/markstream-vue
Override built-in Markstream node renderers and add trusted custom tags across Vue, React, Svelte, and Angular.
Screenmap
aleqsio/screenmap
Generate a visual navigation map of an Expo / React Native or NativeScript app.
Markstream Install
Simon-He95/markstream-vue
Install and wire markstream-vue, markstream-react, markstream-vue2, markstream-angular, or markstream-svelte into an existing repository.
More from inkline/inkline
All 23 skills in this repoAdversarial QA
inkline/inkline
Repro-first QA for Inkline — minimal .ink.tsx reproductions, the visual-parity and cross-target harnesses, fuzz targets, and how to audit teammates' claims.
Benchmark Protocol
inkline/inkline
How Inkline measures itself — compile performance, output size and quality vs hand-written components and Mitosis, fairness rules, and reporting format.
Compiler Pipeline Internals
inkline/inkline
The Inkline compiler's end-to-end pipeline — parse → IR → analyze → per-target codegen → print — including the IR contracts, reactivity tracking, target rewrite rules, plugin hooks, the two compile…
Component Catalog
inkline/inkline
How Inkline components are built and kept consistent — the headless/styled split, family anatomy, prop/axis conventions, recipe consumption, the current 5-family catalog and its gap list.
Create PR
inkline/inkline
Author a pull request in the Guild's standard shape — a fixed Summary / Changes / Verification / Notes skeleton that mirrors the review-gate, plus the hard anti-leak rule that no agent @mention or…
Design Token Architecture
inkline/inkline
How design tokens and recipes flow from styleframe into Inkline — the presets, the two faces of virtual:styleframe, recipe class contracts, theming, and the rules for custom CSS in components.
Related
Questions about Test Component
What does Test Component do?
Phase 4 of building an Inkline component — write colocated cross-target tests. Test Component is an agent skill from inkline/inkline. Phase 4 of building an Inkline component — write colocated cross-target tests.
When should I use Test Component?
Test Component fits situations like: strengthening a components tests.
How do I install Test Component in Claude Code?
Run `npx skills add inkline/inkline --skill test-component -a claude-code`. Or copy the skill folder (.claude/skills/test-component in inkline/inkline) into .claude/skills/test-component in your project. Claude Code loads it when a task matches its description.
How do I install Test Component in Codex?
Run `npx skills add inkline/inkline --skill test-component -a codex`. Or copy the skill folder (.claude/skills/test-component in inkline/inkline) into .agents/skills/test-component in your project. Codex loads it when a task matches its description.
Can I use Test Component 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 inkline/inkline --skill test-component -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-component, .gemini/skills/test-component, .github/skills/test-component and .opencode/skills/test-component in your project.
What does Test Component need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Component is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob.
Does Test Component 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 Test Component safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Test Component use?
No licence was found for Test Component or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Test Component use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Test Component?
Skills that share tags, products or a category with Test Component: Boneyard (0xGF/boneyard, 7.5k stars), Feature Sync (NG-ZORRO/ng-zorro-antd, 9.2k stars), Winui App (LanceMcCarthy/DevOpsExamples, 172 stars) and Markstream Custom Components (Simon-He95/markstream-vue, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Component?
inkline (a GitHub organization) maintains it in inkline/inkline, which has 1,469 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 11, 2026.
Source: inkline/inkline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.