skill

Direct users to the canonical skill implementation at cnos.core.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill skill-usurobor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.eng/skills/eng/skill
Command: npx skills add https://github.com/usurobor/cnos --skill skill-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecated placeholder Skill that preserves the interface while directing users to the canonical implementation in cnos.core.

Core Features & Use Cases

  • Placeholder for Skill API compatibility during migration.
  • Used in documentation and during transition to the canonical skill location.
  • Example: developers reference the canonical path to activate the actual skill.

Quick Start

Refer to the canonical Skill at cnos.core/skills/skill/SKILL.md to use the real implementation.

Frequently Asked Questions about skill

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

FAQPage Schema
How do I migrate a deprecated skill to a canonical path during a transition phase?

To migrate a deprecated skill, reference the canonical path at cnos.core/skills/skill/SKILL.md to activate the real implementation. The deprecated placeholder preserves API compatibility while directing users to the new location.

What is a deprecated placeholder skill used for in documentation contexts?

A deprecated placeholder skill is used to preserve the Skill API interface during migration while guiding users to the canonical implementation in cnos.core for documentation and transition phases.

Does the deprecated skill still satisfy frontmatter requirements after migration?

Yes, the deprecated placeholder skill satisfies frontmatter requirements by preserving the name and description fields, while the body references the canonical path in cnos.core for the actual implementation.

Why does the canonical skill reference cnos.core instead of running directly?

The canonical skill moved to cnos.core to consolidate the implementation. The deprecated stub preserves interface compatibility but does not run directly, requiring users to reference the canonical path for the real skill.

When should I not use the deprecated skill stub for development?

You should not use the deprecated skill stub for active development because it only serves as a placeholder. You must reference the canonical implementation at cnos.core/skills/skill/SKILL.md for the actual functionality.