Skip to content
FunCoding

Search

Search docs, Skills and MCP

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.

数据库与数据1.1kskills/manage-local-skills/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/tencentcloudbase/cloudbase-ai-toolkit/manage-local-skills/install.md ，按里面的步骤帮我安装这个 Skill。

SKILL.md

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?

Similar Skills

xlsx
anthropics/skills180k

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

Databases & data

deprecation-and-migration
addyosmani/agent-skills103k

deprecation-and-migration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

Databases & data

host-observer
thedotmack/claude-mem98k

host-observer

Use this when fulfilling claude-mem observer jobs on Grok Bot: reply only skip_summary or one full observation XML, never prose.

Databases & data

babysit
thedotmack/claude-mem98k

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

Databases & data

mem-search
thedotmack/claude-mem98k

mem-search

Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

Databases & data

Agent Cost Report
thedotmack/claude-mem98k

Agent Cost Report

Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

Databases & data