skill

Manage local AI assistant skills via a unified CLI across user and project scopes.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Linnanli/xClaw --skill skill-linnanli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill
Source: https://github.com/Linnanli/xClaw/tree/main/.codex/skills/skill
Command: npx skills add https://github.com/Linnanli/xClaw --skill skill-linnanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and manage local skill definitions for the AI assistant across user and project scopes, enabling discovery, consistency, and on-demand activation of skills.

Core Features & Use Cases

  • Unified CLI to list, add, remove, search, edit, setup, and synchronize skills
  • Supports both user (~/.codex/skills) and project (.codex/skills) scopes
  • Templates and interactive prompts to accelerate skill creation and maintenance

Quick Start

Create a new skill with '/skill add <name>' and manage it with '/skill list' and '/skill edit <name>'.

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 for my AI assistant using a CLI?

You can manage local AI assistant skills using a unified CLI to list, add, remove, edit, search, setup, and synchronize definitions across user and project scopes.

What is the file structure required to define a local skill?

A local skill requires a SKILL.md file at the root with YAML frontmatter containing the name and description, alongside optional subdirectories for scripts, references, and assets.

Can I organize AI skills separately for global user and specific project scopes?

Yes, you can organize AI skills across distinct scopes, supporting both global user configurations in the ~/.codex/skills directory and project-specific setups in the .codex/skills directory.

How do I create a new local skill definition from the command line?

To create a new local skill definition, use the '/skill add <name>' command, which leverages templates and interactive prompts to accelerate skill creation and maintenance.

What is the best way to keep local skill definitions consistent across different environments?

The best way to keep local skill definitions consistent is to use the built-in synchronization feature, ensuring on-demand activation and uniform skill discovery across user and project scopes.

Are there interactive prompts available for editing and maintaining local skills?

Yes, interactive prompts and templates are provided to accelerate skill creation and maintenance, guiding you through the process when adding or editing local skill definitions.