One-click install
npx skills add https://github.com/cheetah-alo/NegritaOS --skill skill-sync-cheetah-alo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-sync
Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/skill-sync
Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill skill-sync-cheetah-alo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Skill-sync prevents AGENTS.md “Auto-invoke Skills” tables from becoming stale or inconsistent after you create or update skills.

Core Features & Use Cases

  • Metadata-driven synchronization: Reads each skill’s SKILL.md frontmatter (metadata.scope and metadata.auto_invoke) and regenerates the corresponding Auto-invoke table(s).
  • Multi-scope support: Updates the correct AGENTS.md file(s) based on scopes such as root, frontend, backend, data_analytics, and mcp_server.
  • Deterministic outputs and safe updates: Uses deterministic ordering for stable diffs and replaces or inserts the Auto-invoke section idempotently.

Quick Start

Run the skill-sync script to regenerate AGENTS.md auto-invoke tables after you modify any skill metadata.

Frequently Asked Questions about skill-sync

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

FAQPage Schema
How do I keep AGENTS.md auto-invoke tables in sync with SKILL.md metadata?

Synchronizing AGENTS.md auto-invoke tables involves parsing YAML frontmatter from SKILL.md files and regenerating markdown tables deterministically to prevent stale or inconsistent entries.

What is the best way to update auto-invoke tables after modifying skill metadata?

Updating auto-invoke tables requires reading metadata.scope and metadata.auto_invoke from SKILL.md frontmatter, then mapping those scopes to specific AGENTS.md targets for deterministic markdown generation.

Does skill-sync support multi-scope AGENTS.md targets like frontend and backend?

Multi-scope support updates the correct AGENTS.md files based on scopes such as root, frontend, backend, data_analytics, and mcp_server by mapping frontmatter scopes to specific targets.

How do I troubleshoot missing auto-invoke entries in AGENTS.md tables?

Troubleshooting missing auto-invoke entries requires verifying that metadata.scope and metadata.auto_invoke are properly declared in SKILL.md frontmatter, then regenerating tables to insert sections idempotently.

Can I prevent duplicate sections when regenerating markdown tables for auto-invoke skills?

Preventing duplicate sections uses deterministic ordering for stable diffs and replaces or inserts the Auto-invoke section idempotently, ensuring safe updates without redundant markdown table blocks.

When do I need to regenerate AGENTS.md auto-invoke tables?

Regenerating AGENTS.md auto-invoke tables is needed when creating or modifying skills that include metadata.scope and metadata.auto_invoke declarations in their SKILL.md YAML frontmatter.