Agent skill

Check

Verify all outputs exist after creating a new component and fix any issues

MITAuto-check passedDevelopment

Install Check

skills CLI

$ npx skills add alamenai/terrae --skill check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install alamenai/terrae check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/check .claude/skills/check && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "check" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/check into .claude/skills/check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check", 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

$skill-installer install https://github.com/alamenai/terrae/tree/main/.claude/skills/check

Type 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.

skills CLI

$ npx skills add alamenai/terrae --skill check -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install alamenai/terrae check --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/check .agents/skills/check && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "check" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/check into .agents/skills/check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check", 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.

skills CLI

$ npx skills add alamenai/terrae --skill check -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install alamenai/terrae check --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/check .cursor/skills/check && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "check" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/check into .cursor/skills/check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check", 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

$ gemini skills install https://github.com/alamenai/terrae.git --path .claude/skills/check

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add alamenai/terrae --skill check -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install alamenai/terrae check --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/check .gemini/skills/check && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "check" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/check into .gemini/skills/check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check", 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.

GitHub CLI

$ gh skill install alamenai/terrae check

Installs 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).

skills CLI

$ npx skills add alamenai/terrae --skill check -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/check .github/skills/check && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "check" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/check into .github/skills/check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check", 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.

skills CLI

$ npx skills add alamenai/terrae --skill check -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install alamenai/terrae check --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alamenai/terrae.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/check .opencode/skills/check && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "check" agent skill from https://github.com/alamenai/terrae/tree/main/.claude/skills/check into .opencode/skills/check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check", 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: check
GitHub stars: 244
Token cost: ~1.1k tokens
SKILL.md length: 473 words
Files: 1
Skills in repo: 11
Repo updated: Apr 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Verify all outputs exist after creating a new component and fix any issues

Works in 4 steps: Work through issues in check order (1–8) → Apply the minimal change needed for each… → After all fixes, re-run the checks to… → …
Development work in your project
SKILL.md covers Instructions, Output Format and Fix Phase
Reaches terrae.dev; needs NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN

What it does

Check is an agent skill from alamenai/terrae. Verify all outputs exist after creating a new component and fix any issues

Its SKILL.md is about 1.1k 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 Development. It works with Mapbox and React. The repository describes itself as: Composable and animated components that replace imperative layers with simple props. The perfect companion for shadcn/ui. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/check”

Requirements

A credential in NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Work through issues in check order (1–8)
Apply the minimal change needed for each issue
After all fixes, re-run the checks to confirm everything passes
Present the updated checklist table showing all checks as pass

What it can do on your machine

Read from SKILL.md and the folder at commit ea9a480. 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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- terrae.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Check loads about 1.1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 473 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~20
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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 alamenai/terrae at commit ea9a480, republished under its MIT licence (© alamenai). 473 words, ~1,137 tokens.

Download SKILL.mdSave it as .claude/skills/check/SKILL.md (or your agent's skills folder).

name: check
description: Verify all outputs exist after creating a new component and fix any issues
argument-hint: component-name

Check Component Skill

Verify that all 8 required outputs exist and are wired correctly after creating a new component.

Instructions

Given a component name (e.g., cyclone, MapCyclone), normalize it to its kebab-case slug (e.g., cyclone) and run through every check below.

Check 1: Component Source File

File exists: src/registry/map/{slug}.tsx
Has "use client" directive (if it uses hooks, event handlers, or browser APIs)
Exports a named component (e.g., MapCyclone)
Uses type not interface for type definitions
Uses arrow functions with explicit returns
Default values use SCREAMING_SNAKE_CASE constants above the component
Required props come before optional props in the type definition
Cleanup in useEffect return functions (removes layers, sources, markers, event listeners)

Check 2: Barrel Export

src/registry/map/index.tsx has an export line for the component
If the component exposes a control hook, it is also exported (e.g., useCycloneControl)

Check 3: Registry Entry

registry.json has an entry in items with:
- name in kebab-case (e.g., cyclone)
- registryDependencies includes "https://www.terrae.dev/map.json"
- files[0].path matches the source file path
- files[0].target follows components/ui/map/{slug}.tsx

Check 4: Example Files

At least one example exists: src/app/docs/_components/examples/{slug}-example.tsx
Examples import from @/registry/map
Examples wrap the map in <div className="h-full w-full">
Examples use process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || "" as access token
Examples that use hooks or event handlers have "use client"

Check 5: Documentation Page

File exists: src/app/docs/{slug}/page.tsx
Exports metadata with a title
Uses DocsLayout with title, description, prev, and next
First section is "Installation" with two CodeBlocks (base map + component)
Basic ComponentPreview appears directly after Installation
Every example rendered on the page has a matching getExampleSource call
If the component has configurable props, a properties Table section exists
All documented props match the actual component props (no missing, no extra)

Show full SKILL.md (202 more words)Show less

src/app/docs/_components/docs-sidebar.tsx has a NavItem for the component
The href matches /docs/{slug}
Has badge: "new"
Placed in the correct section ("Core" or "Features")
The Lucide icon is imported

Check 7: Components Page

src/app/docs/components/page.tsx has a ComponentItem entry
The href matches /docs/{slug}
Has isNew: true
category matches the sidebar section
installCommand URL matches https://www.terrae.dev/{registry-name}.json
The Lucide icon is imported

Check 8: Changelog

src/app/docs/changelog/page.tsx has an entry in the most recent ChangelogEntry
Entry has title, description (with <code> tag for component name), and href
href matches /docs/{slug}

Output Format

Present results as a checklist table:

| #   | Output             | Status | Notes                   |
| --- | ------------------ | ------ | ----------------------- |
| 1   | Component source   | pass   |                         |
| 2   | Barrel export      | pass   |                         |
| 3   | Registry entry     | fail   | Missing target path     |
| 4   | Examples           | pass   | 3 examples found        |
| 5   | Documentation page | warn   | Missing props: `scale`  |
| 6   | Sidebar navigation | pass   |                         |
| 7   | Components page    | pass   |                         |
| 8   | Changelog          | pass   |                         |

pass: Everything correct
warn: Works but has minor issues (e.g., missing optional prop in docs table)
fail: Missing or broken, needs fixing

After the table, list specific issues with file paths and line numbers.

Fix Phase

If any checks have fail or warn status, fix them automatically:

Work through issues in check order (1–8)
Apply the minimal change needed for each issue
After all fixes, re-run the checks to confirm everything passes
Present the updated checklist table showing all checks as pass

If a fix requires a decision (e.g., which sidebar section to place the component in), ask the user before proceeding.

Files

Just SKILL.md in .claude/skills/check of alamenai/terrae.

Open the folder on GitHubat commit ea9a480

Compare with similar skills

Check 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.

Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Check this skillalamenai/terrae	244	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Vercel Composition Patternssupabase/supabase	111k	58 repos	~726	Automated safety check: Pass	MIT	today
Electron Multi-Process ArchitectureiOfficeAI/AionUi	33k	1 repos	~1.8k	Automated safety check: Pass	Apache-2.0	1 mo ago
Nx Generatenomcopter/react-mosaic	4.8k	7 repos	~1.9k	Automated safety check: Pass	Custom licence	11 days ago
@pierre/diffs Code Renderingpierrecomputer/pierre	6.3k	2 repos	~803	Automated safety check: Pass	Apache-2.0	yesterday
OpenTUI Terminal Interfacescline/cline	70k	—	~1.9k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 58 repos~726 tokens
DevelopmentAuto-check passed
Electron Multi-Process Architecture
iOfficeAI/AionUi
Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.
33k GitHub starsUsed in 1 repo~1.8k tokens
DevelopmentAuto-check passed
Nx Generate
nomcopter/react-mosaic
Generate code using nx generators. An agent skill from nomcopter/react-mosaic.
4.8k GitHub starsUsed in 7 repos~1.9k tokens
DevelopmentAuto-check passed
@pierre/diffs Code Rendering
pierrecomputer/pierre
Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.
6.3k GitHub starsUsed in 2 repos~803 tokens
DevelopmentAuto-check passed
OpenTUI Terminal Interfaces
cline/cline
Helps build terminal user interfaces with OpenTUI using its core imperative API or its React and Solid reconcilers, with references for layout, keyboard, animation and testing.
70k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Claude Code Skill
codeaashu/claude-code
Development conventions and architecture guide for the Claude Code CLI repository.
3.4k GitHub starsUsed in 1 repo~2.7k tokens
DevelopmentAuto-check passed

Questions about Check

What does Check do?

Verify all outputs exist after creating a new component and fix any issues. Check is an agent skill from alamenai/terrae.

When should I use Check?

Check fits situations like: development work in your project.

How do I install Check in Claude Code?

Run `npx skills add alamenai/terrae --skill check -a claude-code`. Or copy the skill folder (.claude/skills/check in alamenai/terrae) into .claude/skills/check in your project. Claude Code loads it when a task matches its description.

How do I install Check in Codex?

Run `npx skills add alamenai/terrae --skill check -a codex`. Or copy the skill folder (.claude/skills/check in alamenai/terrae) into .agents/skills/check in your project. Codex loads it when a task matches its description.

Can I use Check 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 alamenai/terrae --skill check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check, .gemini/skills/check, .github/skills/check and .opencode/skills/check in your project.

What does Check need to run?

Going by SKILL.md and its folder, Check needs credentials named NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN. Our summary lists: A credential in NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN.

Does Check access the network?

SKILL.md names 1 domain. In commands or code: terrae.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Check 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 Check use?

Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Check use?

About 1.1k tokens (SKILL.md is roughly 4.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 Check?

Skills that share tags, products or a category with Check: Vercel Composition Patterns (supabase/supabase, 111k stars), Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars), Nx Generate (nomcopter/react-mosaic, 4.8k stars) and @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check?

alamenai (a GitHub user) maintains it in alamenai/terrae, which has 244 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on April 6, 2026.

Source: alamenai/terrae on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Check Component Skill

Instructions

Check 1: Component Source File

Check 2: Barrel Export

Check 3: Registry Entry

Check 4: Example Files

Check 5: Documentation Page

Check 6: Sidebar Navigation

Check 7: Components Page

Check 8: Changelog

Output Format

Fix Phase

Files

Compare with similar skills

Similar skills

More from alamenai/terrae

Related

Questions about Check