Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Run TypeScript compilation and lint checks for an OpenCRVS package after modifying or adding files under packages/{packagename}.
Install Compile Lint Check
$ npx skills add opencrvs/opencrvs-core --skill compile-lint-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opencrvs/opencrvs-core compile-lint-check --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/opencrvs/opencrvs-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/compile-lint-check .claude/skills/compile-lint-check && 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 "compile-lint-check" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-check into .claude/skills/compile-lint-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compile-lint-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 install https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-checkType 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 opencrvs/opencrvs-core --skill compile-lint-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opencrvs/opencrvs-core compile-lint-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/compile-lint-check .agents/skills/compile-lint-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "compile-lint-check" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-check into .agents/skills/compile-lint-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compile-lint-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.
$ npx skills add opencrvs/opencrvs-core --skill compile-lint-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opencrvs/opencrvs-core compile-lint-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/compile-lint-check .cursor/skills/compile-lint-check && 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 "compile-lint-check" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-check into .cursor/skills/compile-lint-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compile-lint-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 https://github.com/opencrvs/opencrvs-core.git --path .claude/skills/compile-lint-check--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 opencrvs/opencrvs-core --skill compile-lint-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opencrvs/opencrvs-core compile-lint-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/compile-lint-check .gemini/skills/compile-lint-check && 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 "compile-lint-check" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-check into .gemini/skills/compile-lint-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compile-lint-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.
$ gh skill install opencrvs/opencrvs-core compile-lint-checkInstalls 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 opencrvs/opencrvs-core --skill compile-lint-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/compile-lint-check .github/skills/compile-lint-check && 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 "compile-lint-check" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-check into .github/skills/compile-lint-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compile-lint-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.
$ npx skills add opencrvs/opencrvs-core --skill compile-lint-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opencrvs/opencrvs-core compile-lint-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/compile-lint-check .opencode/skills/compile-lint-check && 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 "compile-lint-check" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/compile-lint-check into .opencode/skills/compile-lint-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compile-lint-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
compile-lint-check- GitHub stars
- 120
- Token cost
- ~237 tokens
- SKILL.md length
- 86 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Run TypeScript compilation and lint checks for an OpenCRVS package after modifying or adding files under packages/{packagename}.
- Tasks that involve Linting and formatting
- Calls nx and pnpm
What it does
Compile Lint Check is an agent skill from opencrvs/opencrvs-core. Run TypeScript compilation and lint checks for an OpenCRVS package after modifying or adding files under packages/{packagename}. Invoke immediately after edits, not just at session end.
Its SKILL.md is about 240 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, covering Linting and formatting. It works with TypeScript. The repository describes itself as: A global solution to civil registration.
When your agent uses it
- Tasks that involve Linting and formatting
Example prompts
- “/compile-lint-check”
Requirements
- Pre-approved tools (allowed-tools): Bash
What it can do on your machine
Read from SKILL.md and the folder at commit ab91cce. 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:
Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
nxpnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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
Compile Lint Check loads about 237 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 86 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: Bash
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 86 words (~237 tokens).
“Get {package_name} from the edited file's path under packages/, then run:”
- name
- compile-lint-check
- allowed-tools
- Bash
Files
Just SKILL.md in .claude/skills/compile-lint-check of opencrvs/opencrvs-core.
Open the folder on GitHubat commit ab91cce
Compare with similar skills
Compile Lint 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Compile Lint Check this skillopencrvs/opencrvs-core | 120 | — | ~237 | Automated safety check: Notes | Custom licence | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.3k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Eslint Migrate Optionsbiomejs/biome | 26k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Ultraciteagustinusnathaniel/nextarter-tailwind | 125 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Find Similar Functionsmillionco/react-doctor | 15k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Eslint Migrate Options
biomejs/biome
A skill your agent uses when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures.
Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
Find Similar Functions
millionco/react-doctor
Use truffler to find similar or pre-existing JavaScript/TypeScript symbols before implementing new code, especially helpers, utilities, parsers, formatters, scanners, fuzzy matchers, and other…
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
Boundaries Architect
javierbrea/eslint-plugin-boundaries
Act as a software architect: analyze a repository's folder structure and cross-file import dependencies, detect its architectural pattern, design element/file boundaries with the user, and configure…
More from opencrvs/opencrvs-core
Release Prep
opencrvs/opencrvs-core
Entry point for preparing an OpenCRVS core release — lists the release-prep tasks and gathers what changed in the release.
Grilling
opencrvs/opencrvs-core
Grill the user relentlessly about a plan or design. An agent skill from opencrvs/opencrvs-core.
PR Desc
opencrvs/opencrvs-core
A skill your agent uses when the user asks to write, update, or amend a GitHub PR description — e.g.
Release Docs Sync
opencrvs/opencrvs-core
Make the v<version.0 directory of the opencrvs/documentation repo reflect what an OpenCRVS core release ships — find missing and outdated pages, draft the edits on a branch.
Related
Works with
Categories
Questions about Compile Lint Check
What does Compile Lint Check do?
Run TypeScript compilation and lint checks for an OpenCRVS package after modifying or adding files under packages/{packagename}. Compile Lint Check is an agent skill from opencrvs/opencrvs-core. Run TypeScript compilation and lint checks for an OpenCRVS package after modifying or adding files under packages/{packagename}.
When should I use Compile Lint Check?
Compile Lint Check fits situations like: tasks that involve Linting and formatting.
How do I install Compile Lint Check in Claude Code?
Run `npx skills add opencrvs/opencrvs-core --skill compile-lint-check -a claude-code`. Or copy the skill folder (.claude/skills/compile-lint-check in opencrvs/opencrvs-core) into .claude/skills/compile-lint-check in your project. Claude Code loads it when a task matches its description.
How do I install Compile Lint Check in Codex?
Run `npx skills add opencrvs/opencrvs-core --skill compile-lint-check -a codex`. Or copy the skill folder (.claude/skills/compile-lint-check in opencrvs/opencrvs-core) into .agents/skills/compile-lint-check in your project. Codex loads it when a task matches its description.
Can I use Compile Lint 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 opencrvs/opencrvs-core --skill compile-lint-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/compile-lint-check, .gemini/skills/compile-lint-check, .github/skills/compile-lint-check and .opencode/skills/compile-lint-check in your project.
What does Compile Lint Check need to run?
Going by SKILL.md and its folder, Compile Lint Check needs the command-line tools its instructions call (nx and pnpm). Its frontmatter pre-approves these tools: Bash.
Does Compile Lint Check 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 Compile Lint Check 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 Compile Lint Check use?
Compile Lint Check 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 Compile Lint Check use?
About 237 tokens (SKILL.md is roughly 948 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 Compile Lint Check?
Skills that share tags, products or a category with Compile Lint Check: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Eslint Migrate Options (biomejs/biome, 26k stars), Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars) and Find Similar Functions (millionco/react-doctor, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Compile Lint Check?
opencrvs (a GitHub organization) maintains it in opencrvs/opencrvs-core, which has 120 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.
Source: opencrvs/opencrvs-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.