New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cabloy Module Removal

by cabloy in cabloy/cabloy

A skill your agent uses whenever the user wants to remove or delete an existing Cabloy module, retire a demo module, or cleanly take a backend, frontend, or fullstack module out of the monorepo.

MITAuto-check passedDevelopment

Install Cabloy Module Removal

skills CLI
$ npx skills add cabloy/cabloy --skill cabloy-module-removal -a claude-code

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

GitHub CLI
$ gh skill install cabloy/cabloy cabloy-module-removal --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/cabloy/cabloy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cabloy-module-removal .claude/skills/cabloy-module-removal && 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/

Facts

Skill name
cabloy-module-removal
GitHub stars
982
Token cost
~1.5k tokens
SKILL.md length
743 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses whenever the user wants to remove or delete an existing Cabloy module, retire a demo module, or cleanly take a backend, frontend, or fullstack module out of the monorepo.

  • Works in 6 steps: Detect repo and classify the removal… → Inventory real source and direct… → Keep the normal execution order… → …
  • The user wants to remove
  • SKILL.md covers Goals, Step 1: Detect repo and…, Step 2: Inventory real source… and Step 3: Keep the normal…, plus 4 more sections
  • Calls npm

What it does

Cabloy Module Removal is an agent skill from cabloy/cabloy. Use this skill whenever the user wants to remove or delete an existing Cabloy module, retire a demo module, or cleanly take a backend, frontend, or fullstack module out of the monorepo. Trigger for requests such as remove module, delete module, retire module, remove demo module, or remove fullstack module, including equivalent requests in other languages. Prefer it when the task is about deletion order, generated-runtime cleanup, and verification rather than scaffolding or contract evolution.

Its SKILL.md is about 1.5k 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 Monorepo tooling and Project scaffolding. The repository describes itself as: Cabloy is a Node.js fullstack framework for AI vibe coding, with AI Spec-Driven Development guiding work from confirmed specs to verifiable delivery. The licence is MIT.

When your agent uses it

  • The user wants to remove
  • Delete an existing Cabloy module
  • Retire a demo module
  • Cleanly take a backend

Example prompts

  • “/cabloy-module-removal”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Detect repo and classify the removal branch
  2. Inventory real source and direct references first
  3. Keep the normal execution order source-first
  4. Use generated-runtime cleanup only as a recovery branch
  5. Finish with branch-aware verification
  6. Treat docs cleanup as a separate scope decision

What it can do on your machine

Read from SKILL.md and the folder at commit afa6a6d. 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:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, 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

Cabloy Module Removal loads about 1.5k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 743 words of instructions outside code blocks.

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

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 cabloy/cabloy at commit afa6a6d, republished under its MIT licence (© cabloy). 743 words, ~1,466 tokens.

Download SKILL.mdSave it as .claude/skills/cabloy-module-removal/SKILL.md (or your agent's skills folder).
name
cabloy-module-removal
description
Use this skill whenever the user wants to remove or delete an existing Cabloy module, retire a demo module, or cleanly take a backend, frontend, or fullstack module out of the monorepo. Trigger for requests such as remove module, delete module, retire module, remove demo module, or remove fullstack module, including equivalent requests in other languages. Prefer it when the task is about deletion order, generated-runtime cleanup, and verification rather than scaffolding or contract evolution.

Cabloy Module Removal

Use this skill when the user wants to remove an existing module from the Cabloy monorepo.

Read the public Module Removal Playbook for the canonical user/agent-facing workflow. This skill is the thinner orchestration layer: it should classify the removal path, choose the right cleanup branch, and point back to the playbook for the shared operational sequence.

Goals

  1. detect whether the active repository is Cabloy Basic or Cabloy Start
  2. classify the removal scope as backend-only, frontend-only, or fullstack
  3. keep the workflow source-first instead of debugging generated artifacts too early
  4. make the stale-generated-runtime recovery branch explicit when needed
  5. finish with verification guidance that proves the module is gone from the runtime/code graph

Step 1: Detect repo and classify the removal branch

Check the repository root for these marker files:

  • __CABLOY_BASIC__
  • __CABLOY_START__

Interpretation:

  • only __CABLOY_BASIC__ present → this is Cabloy Basic
  • only __CABLOY_START__ present → this is Cabloy Start
  • both markers present → treat the repository as ambiguous or invalid and stop before making edition-specific assumptions
  • neither marker present → inspect the owning package scripts and nearby repository structure, then ask before making an edition-specific assumption

Then classify the request into one of three branches:

Branch A: backend-only removal

Use this branch when the user is removing only Vona-side code such as:

  • vona/src/module/<module>
  • backend package references
  • backend tests or metadata tied only to Vona
Branch B: frontend-only removal

Use this branch when the user is removing only Zova-side code such as:

  • zova/src/module/<module>
  • frontend package references
  • Zova-only API/model/component assets
Branch C: fullstack removal

Use this branch when the module exists on both sides or the request affects both Vona and Zova.

This is the default branch for demo modules and shared business threads.

Step 2: Inventory real source and direct references first

Before proposing or making cleanup steps, inspect the real module surfaces first:

  • backend and frontend module roots
  • vona/package.json
  • zova/package.json
  • generated registries or lockfiles that may need refresh
  • tests tied to the module
  • optional docs/examples only if the user explicitly wants a public scrub

Start from the shared root scripts first:

  • package.json
  • npm run vona
  • npm run zova

Do not assume a module lives only in one path family until the actual repo layout has been inspected.

Step 3: Keep the normal execution order source-first

Point the user or the main workflow to this order:

  1. remove backend source if in scope
  2. remove frontend source if in scope
  3. remove direct workspace dependency references
  4. run the repo-owned regeneration flow
  5. verify no references remain

Important rule:

  • do not start by hand-editing generated caches or type surfaces while the real source and dependency references still exist

Use the playbook for the full operational sequence and representative commands.

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

Step 4: Use generated-runtime cleanup only as a recovery branch

When a module has already been removed from source and direct dependency references, but stale generated types or runtime entries still remain, treat generated runtime directories as disposable working state rather than source-of-truth files.

Primary recovery targets for this workflow are:

  • vona/.vona
  • zova/.zova

These directories are auto-generated by the Vona and Zova CLI flows and may survive when a service or build process does not stop cleanly.

This is a recovery branch, not the default first step.

After cleanup, rerun the normal build/deps/typecheck flow from the playbook.

Step 5: Finish with branch-aware verification

Use the verification path that matches the branch:

  • backend-only → backend deps/typecheck/tests as needed
  • frontend-only → relevant Zova build/deps/typecheck path
  • fullstack → fullstack regeneration order plus typecheck and targeted tests

Verification should prove:

  • no direct workspace dependency entries remain
  • no stale generated registrations remain
  • no typecheck failures still point at the removed module
  • no important runtime or test surfaces still import the removed module

Step 6: Treat docs cleanup as a separate scope decision

Do not assume module deletion automatically means public docs cleanup.

Ask or confirm whether the task is:

  • code/runtime removal only
  • code/runtime removal plus docs/examples scrub

If docs cleanup is in scope, update repo-docs/ separately from the runtime cleanup. Keep maintainer rationale in repo-docs-internal/; do not require a particular internal record as part of module removal.

Response pattern

When using this skill, structure the response around these points when helpful:

  1. detected edition
  2. detected removal scope
  3. real module surfaces involved
  4. recommended cleanup/regeneration branch
  5. stale-generated-runtime recovery branch if needed
  6. verification steps

Keep the response practical. The value of this skill is to choose the right removal branch quickly and keep generated working state in the correct role.

© cabloy, MIT. 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 .agents/skills/cabloy-module-removal of cabloy/cabloy.

Open the folder on GitHubat commit afa6a6d

Compare with similar skills

Cabloy Module Removal 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.

Cabloy Module Removal compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cabloy Module Removal this skillcabloy/cabloy982—~1.5kAutomated safety check: PassMIT
Run Nx Generatornrwl/nx29k2 repos~592Automated safety check: NotesMIT
Create Vechain Dappvechain/x-app-template450—~1.8kAutomated safety check: PassMIT
Create Saleor Packagesaleor/apps162—~608Automated safety check: PassCustom licence
Light Project StructureLight0305/Light-skills641—~3kAutomated safety check: NotesMIT
Creating Luna Appmizchi/luna.mbt173—~1.4kAutomated safety check: PassNone

Similar skills

  • Run Nx Generator

    nrwl/nx

    Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes

  • Create Vechain Dapp

    vechain/x-app-template

    Scaffold a VeChain dApp with Next.js, VeChain Kit, Chakra UI v3, and GitHub Pages deployment.

    450 GitHub stars~1.8k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Create Saleor Package

    saleor/apps

    Scaffold a new shared package in the saleor-apps monorepo under ./packages/.

    162 GitHub stars~608 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Light Project Structure

    Light0305/Light-skills

    Audits, scaffolds and safely migrates research project folder structures, keeping existing repositories read-only until you approve exact moves from a plan.

    641 GitHub stars~3k tokensUpdated 3 mo ago
    DevelopmentAuto-check: notes

  • Creating Luna App

    mizchi/luna.mbt

    A skill your agent uses when scaffolding a new standalone CSR app that uses luna (@lunaui/luna) outside the luna.mbt monorepo — running npx @lunaui/luna new, choosing TSX vs MoonBit, or fixing a…

    173 GitHub stars~1.4k tokensUpdated 22 days ago
    DevelopmentAuto-check passed

  • Adk Readme Writer

    BrainDAO/adk-ts

    ADK-TS README specialist. An agent skill from BrainDAO/adk-ts.

    119 GitHub stars~2.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check: notes

More from cabloy/cabloy

All 12 skills in this repo

  • Cabloy Spec Generation

    cabloy/cabloy

    A skill your agent uses to create or maintain Cabloy suite specifications under repo-specs, including PRD, SRS, PDP/WBS, acceptance planning, progress, and suite ADRs.

    982 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check: notes

  • Cabloy Domain Planning

    cabloy/cabloy

    A skill your agent uses whenever the user wants to plan a new business domain in this Cabloy repo, such as CRM, OA, training, ERP, or a similar long-lived domain.

    982 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Cabloy Worktree Environment

    cabloy/cabloy

    This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup.

    982 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check: notes

  • Cabloy Backend Scaffold

    cabloy/cabloy

    This skill should be used when the user needs the Vona backend scaffold/extend path in this Cabloy repo, especially to choose the right npm run vona generator or CRUD command and the required…

    982 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Cabloy Contract Loop

    cabloy/cabloy

    A skill your agent uses whenever a Cabloy task crosses the Vona-to-Zova contract boundary: backend DTO, controller, validation, entity, inferred DTO, or OpenAPI changes that should drive SDK…

    982 GitHub stars~5.1k tokensUpdated yesterday
    Auto-check passed

  • Cabloy Frontend Scaffold

    cabloy/cabloy

    A skill your agent uses whenever the user wants the Zova frontend path in this Cabloy repo: create or extend pages, components, api or model beans, route/query/params work, metadata refresh…

    982 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Cabloy Module Removal

What does Cabloy Module Removal do?

A skill your agent uses whenever the user wants to remove or delete an existing Cabloy module, retire a demo module, or cleanly take a backend, frontend, or fullstack module out of the monorepo. Cabloy Module Removal is an agent skill from cabloy/cabloy. Use this skill whenever the user wants to remove or delete an existing Cabloy module, retire a demo module, or cleanly take a backend, frontend, or fullstack module out of the monorepo.

When should I use Cabloy Module Removal?

Cabloy Module Removal fits situations like: the user wants to remove; delete an existing Cabloy module; retire a demo module; cleanly take a backend.

How do I install Cabloy Module Removal in Claude Code?

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

How do I install Cabloy Module Removal in Codex?

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

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

What does Cabloy Module Removal need to run?

Going by SKILL.md and its folder, Cabloy Module Removal needs the command-line tools its instructions call (npm).

Does Cabloy Module Removal access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cabloy Module Removal 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 Cabloy Module Removal use?

Cabloy Module Removal 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 Cabloy Module Removal use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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 Cabloy Module Removal?

Skills that share tags, products or a category with Cabloy Module Removal: Run Nx Generator (nrwl/nx, 29k stars), Create Vechain Dapp (vechain/x-app-template, 450 stars), Create Saleor Package (saleor/apps, 162 stars) and Light Project Structure (Light0305/Light-skills, 641 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cabloy Module Removal?

cabloy (a GitHub organization) maintains it in cabloy/cabloy, which has 982 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.

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