skill

Manage local skills via CLI across user and project scopes with validation and sync workflows.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill skill-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/skill
Command: npx skills add https://github.com/YeaChan05/Remittance --skill skill-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a unified CLI experience to manage local skills stored in user and project scopes, enabling discovery, activation, and synchronization.

Core Features & Use Cases

  • List, add, remove, search, edit, and setup skills from both user (~/.codex/skills) and project (.codex/skills) locations.
  • Validate and preview metadata before activation, with safe, confirmed destructive actions for removal.
  • Synchronize and compare skills between scopes to avoid drift and ensure consistency.

Quick Start

Run /skill list to view available skills across both scopes and get started with basic management

Frequently Asked Questions about skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage local skills across different project scopes using a CLI?

You can manage local skills across user and project scopes using a CLI that lists, adds, removes, and edits skills while parsing SKILL.md frontmatter to populate discovery metadata for both locations.

How do I synchronize skills between user and project scopes to avoid drift?

To synchronize skills and avoid drift, the CLI compares skills between the user (~/.codex/skills) and project (.codex/skills) scopes, ensuring metadata consistency and structured validation across both locations.

Can I validate SKILL.md frontmatter before activating local skills?

Yes, you can validate and preview SKILL.md frontmatter metadata before activation. The CLI enforces structured validation and safety checks across add, edit, remove, and sync workflows.

What is the best way to safely remove local skills without accidental data loss?

The best way to safely remove local skills is using the CLI's destructive action workflows, which enforce confirmation checks before deleting skill metadata from user or project scopes.

Does the CLI support searching for specific skills across both user and project locations?

Yes, the CLI supports searching for specific skills across both user (~/.codex/skills) and project (.codex/skills) locations, allowing you to discover and filter skills by their parsed metadata.

How do I set up local skills in the .codex/skills directory for the first time?

You can set up local skills by running the CLI setup workflow, which parses SKILL.md content and frontmatter to populate discovery metadata and activate skills within the .codex/skills directory.