skill

Manage local Codex skills across user and project scopes via CLI.

24|2|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill skill-orinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/skill
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill skill-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the management of local Codex skills by providing a centralized CLI to list, add, edit, remove, and organize skills across user and project scopes.

Core Features & Use Cases

  • Unified skill registry across user and project scopes with consistent metadata handling.
  • Interactive and direct modes for skill creation and manipulation.
  • Safe operations with confirmations for destructive actions and YAML validation.
  • Typical use case: you add a new skill named "my-skill" via /skill add and customize its metadata to fit your codebase.

Quick Start

Run /skill add to create a new skill and follow the prompts to customize its metadata.

Frequently Asked Questions about skill

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

FAQPage Schema
How do I manage local Codex skills from the command line?

You can manage local Codex skills using a CLI toolkit to list, add, edit, remove, and organize them across user and project scopes. It provides a structured YAML frontmatter-driven skill registry for consistent metadata handling.

Can I add a new skill and customize its YAML frontmatter interactively?

Yes, you can add a new skill and customize its YAML frontmatter using interactive command modes. The system validates the YAML frontmatter and enforces naming conventions to ensure metadata consistency across your codebase.

Does the skill CLI support both user and project scopes?

The skill CLI supports both user and project scopes, offering a unified skill registry across them. This allows you to organize local skills contextually depending on whether they apply globally or to a specific project.

How do destructive actions like removing a skill work safely?

Destructive actions like removing a skill work safely by triggering safety prompts that require confirmation before execution. This prevents accidental deletions while you manipulate your local skill registry.

What is the best way to organize developer tools and custom skills for a specific codebase?

The best way to organize developer tools and custom skills is by using a centralized CLI that enforces naming conventions and validates YAML frontmatter. This creates a structured, project-scope registry tailored to your codebase.

Are there limitations when using direct command modes to manipulate skills?

When using direct command modes to manipulate skills, operations are constrained by strict YAML frontmatter validation and naming conventions. This ensures structural integrity but requires all metadata to conform to the expected registry format.