curate-skills

Audit repository skills using ASQM scoring and update agent.yaml files.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill curate-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curate-skills
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/curate-skills
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill curate-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a governance workflow to audit, score, tag, and normalize all skills across a repository, ensuring consistent quality and discoverability.

Core Features & Use Cases

  • ASQM-based scoring across four dimensions (agent_native, cognitive, composability, stance) and generation of per-skill agent.yaml.
  • Lifecycle classification (validated, experimental, archive_candidate) based on objective thresholds.
  • Overlaps detection and market positioning to map relationships between skills.
  • Standardized outputs including agent.yaml and README.md, plus a repository-level ASQM_AUDIT.md.

Quick Start

Run curate-skills to scan the repository's skills/, compute ASQM scores, and update agent.yaml and README.md accordingly.

Frequently Asked Questions about curate-skills

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

FAQPage Schema
What is ASQM scoring for skill governance and how does it work?

ASQM scoring audits repository skills across four dimensions: agent_native, cognitive, composability, and stance. It reads agent.yaml or README/SKILL.md to derive objective scores and outputs per-skill agent.yaml updates and a repository-wide ASQM_AUDIT.md.

How do I audit and normalize all skills in my repository?

Run curate-skills to scan the skills/ directory, compute ASQM scores, classify lifecycle statuses, and automatically update agent.yaml and README.md files for consistent governance across all skills.

Can I detect skill overlaps and lifecycle statuses for repository management?

Yes, skill auditing with ASQM detects overlaps and maps market positioning between skills. It classifies lifecycle statuses as validated, experimental, or archive_candidate based on objective scoring thresholds.

Does skill auditing require specific file formats or directory structures?

Skill auditing requires a skills/ directory containing subdirectories with either agent.yaml or README/SKILL.md files. It reads these formats to derive scores, overlaps, and lifecycle statuses, then updates agent.yaml and generates standardized README.md.

What's the best way to standardize skill documentation across a repository?

ASQM-based skill auditing standardizes documentation by computing scores from existing files, generating per-skill agent.yaml updates, writing standardized README.md files, and producing a repository-level ASQM_AUDIT.md for governance.

Why does skill discoverability and quality suffer in large repositories?

Inconsistent documentation and lack of scoring across skills reduces discoverability. Skill auditing applies ASQM scoring, lifecycle classification, and overlap detection to normalize all skills and ensure consistent quality repository-wide.