Skip to content
cccskills
FreePublished on GitHub

manage-local-skills

Analyze, standardize, validate, and sync locally maintained skills into agent skill directories with a `skills` CLI-aligned workflow. Use this skill when Codex needs to turn ad-hoc prompt or rules folders into reusable `SKILL.md`-based skills, install or sync one or more local skills from `./skills` into Claude, Cursor, CodeBuddy, Codex, or similar agent directories, or manage local skill path mappings and symlink or copy installation behavior.

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit
See how to install

Files included (12)

  • SKILL.md4.8 KB
  • references/cli-alignment.md3.3 KB
  • references/install-workflow.md2.9 KB
  • references/mapping-extension.md1.3 KB
  • references/migration-playbook.md2.2 KB
  • references/source-classification.md2.1 KB
  • scripts/inspect-source.mjs4.1 KB
  • scripts/install-skill.mjs2.8 KB
  • scripts/lib/agent-mappings.mjs2.6 KB
  • scripts/lib/install-model.mjs5.4 KB
  • scripts/lib/path-safety.mjs974 B
  • scripts/validate-skill.mjs3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Manage Local Skills

Manage locally maintained skills as reusable, standard skill assets.

What this skill does

Use this skill to:

  • classify local sources as standard skills, non-standard skill-like folders, or mixed repositories
  • convert non-standard local materials into a standard SKILL.md-based structure
  • validate standard skill structure before installation
  • sync one or more local skills into one or more agent skill directories
  • maintain explicit agent and IDE path mappings for local skill installation

Do not use this skill for

  • publishing remote skills registries or package indexes
  • cloning skills from remote repositories
  • interactive marketplace search
  • generic documentation cleanup unrelated to local skill structure

Workflow

  1. Identify whether the user wants analysis only, migration, validation, mapping changes, or installation.
  2. If the source is not obviously standard, read references/source-classification.md and run scripts/inspect-source.mjs first.
  3. If migration is needed, read references/migration-playbook.md and convert the source into a standard skill folder before installation.
  4. Before mounting a skill, read references/cli-alignment.md and references/install-workflow.md to preserve the source-first install model used in this repo.
  5. Use scripts/validate-skill.mjs before and after installation when structure or path correctness is in doubt.
  6. If the target agent is new or unclear, read references/mapping-extension.md before adding or changing mappings.

Common requests

  • "Install this local skill into Claude and Cursor."
  • "Sync everything under ./skills to Codex and CodeBuddy."
  • "Turn this prompts folder into a reusable skill."
  • "Link my local skills into the agent directories for this project."

Routing

TaskReadScript
Understand how this differs from or aligns with skills CLIreferences/cli-alignment.md
Classify local sources and detect migration candidatesreferences/source-classification.mdscripts/inspect-source.mjs
Convert non-standard local folders into standard skillsreferences/migration-playbook.mdscripts/inspect-source.mjs
Install or mount local skills into agent directoriesreferences/install-workflow.mdscripts/install-skill.mjs
Add or update agent mappingsreferences/mapping-extension.mdscripts/install-skill.mjs
Validate structure or installation resultsreferences/install-workflow.mdscripts/validate-skill.mjs

Operating rules

  • Treat skills CLI installation semantics as the baseline, but follow this repo's source-first project install model for locally maintained skills.
  • Prefer analysis first when the source structure is ambiguous.
  • Do not execute arbitrary scripts from the source folder while inspecting it.
  • In symlink mode, keep skills/ as the single maintained source of truth and expose .agents entries as links instead of extra copies.
  • Prefer symlinks when supported and safe. Fall back to copy when the user requests it or symlinks fail.
  • Make scope explicit: project means the current workspace, global means the user-level agent directory.
  • Ask the user to confirm before writing files, replacing existing installs, changing mappings, or converting a non-standard source into a standard skill.
  • If the user asks to sync multiple skills or multiple agents, summarize the planned batch operation before execution and wait for confirmation.
  • Call out differences whenever the requested behavior cannot fully match skills CLI.

Quick commands

node skills/manage-local-skills/scripts/inspect-source.mjs --input <path> --json
node skills/manage-local-skills/scripts/validate-skill.mjs --skill-dir <path>
node skills/manage-local-skills/scripts/install-skill.mjs --source-dir skills --skill <name> --agent cursor --scope project --mode symlink

Minimum self-check

  • Is the source clearly classified as standard, nonstandard, or mixed?
  • Is the target skill structure valid before installation?
  • If symlink mode was requested, does the installed .agents entry resolve back to the maintained source?
  • Is the selected agent mapping explicit and correct for the requested scope?
  • If symlink mode is used, is there a defined fallback to copy mode?
  • If behavior differs from skills CLI, did you state the difference clearly?

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ai-model-nodejs

Free

Use this skill for Node.js backend AI via @cloudbase/node-sdk (>=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration. The only SDK supporting image generation (ai.createImageModel + generateImage). Text via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*; model ids (e.g. deepseek-v4-flash, glm-5, kimi-k2.6) go in the `model` field of generateText/streamText. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web) or Mini Program (use ai-model-wechat).

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit1.1KUpdated Oct 19, 2026

ai-model-web

Free

Use this skill when a browser/Web app (React, Vue, Next, Nuxt, static sites, SPAs, dashboards, AI chat UI, 页面, 前端, 网页) needs AI models via @cloudbase/js-sdk. Default routing for Web/frontend AI — call directly from the browser, do NOT propose a Node.js proxy. Covers generateText and streamText; models via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*, model id in the `model` field. MUST run two-step preflight before code — see body. NOT for Node.js backend (use ai-model-nodejs), Mini Program (use ai-model-wechat), or image generation (Node SDK only).

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit1.1KUpdated Oct 19, 2026

ai-model-wechat

Free

Use this skill for WeChat Mini Program AI via wx.cloud.extend.AI (小程序, wx.cloud apps). Covers generateText and streamText with callbacks (onText, onEvent, onFinish); streamText needs a data wrapper, generateText returns the raw response. Models via wx.cloud.extend.AI.createModel with groups hunyuan-exp (小程序成长计划), cloudbase (main managed), or custom-*; model id goes in the data wrapper `model` field. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web), Node.js backend (use ai-model-nodejs), or image generation (use ai-model-nodejs).

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit1.1KUpdated Oct 19, 2026

api-contract-review

Free

Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit1.1KUpdated Oct 19, 2026

auth-nodejs-cloudbase

Free

CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit1.1KUpdated Oct 19, 2026

auth-tool-cloudbase

Free

CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to inspect, enable, disable, or configure auth providers, publishable-key prerequisites, login methods, SMS/email sender setup, or other provider-side readiness before implementing a client or backend auth flow.

The English summary is being prepared. Showing the original description.

TencentCloudBase/CloudBase-AI-Toolkit1.1KUpdated Oct 19, 2026

See all skills by TencentCloudBase

Report a problem with this skill