register-and-flag

Register scaffolded extensions in scope-routed registries and track adoption tasks.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Largo2z9/phantomos --skill register-and-flag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: register-and-flag
Source: https://github.com/Largo2z9/phantomos/tree/main/.skills/skills/register-and-flag
Command: npx skills add https://github.com/Largo2z9/phantomos --skill register-and-flag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents newly scaffolded extensions from being forgotten or disconnected by registering them in the correct scope registry and creating adoption tracking entries.

Core Features & Use Cases

  • Scope-Based Registration: Adds custom entities to the appropriate brand, operator, or workspace extensions registry using the current canonical format.
  • Adoption Tracking: Creates todo entries for newly created extensions while avoiding duplicate tracking records.
  • Validation-Aware Workflow: Supports idempotent writes, legacy read fallback handling, and post-write validation expectations for extension pipelines.

Quick Start

Ask the AI to register the newly scaffolded extension in the correct registry and flag it for adoption.

Frequently Asked Questions about register-and-flag

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

FAQPage Schema
How do I register scaffolded extensions in a scope-routed registry?

Register scaffolded extensions by adding custom entities to the appropriate brand, operator, or workspace registry using the current canonical format. This ensures newly created extensions are properly scoped and discoverable within extension lifecycle workflows.

What is extension adoption tracking and why do I need it after scaffolding?

Extension adoption tracking creates todo entries for newly scaffolded extensions to prevent them from being forgotten or disconnected. It avoids duplicate tracking records and ensures follow-up tasks are visible during the extension lifecycle.

How do I ensure idempotent writes when registering extensions in canonical registry files?

Idempotent writes during extension registration are ensured through schema validation and legacy read fallback handling. Post-write validation confirms the extension pipeline correctly processed the registry update without creating duplicate entries.

Does extension registration work with brand, operator, and workspace scope registries?

Extension registration supports brand, operator, and workspace scope-routed registries. It applies scope-based registration to add custom entities to the correct registry using the canonical format required by each specific scope.

What happens if extension discovery pipelines encounter legacy registry formats?

Legacy registry formats are handled through read fallback support during extension registration. The workflow applies schema validation and idempotent writes to maintain compatibility with extension discovery pipelines while transitioning to canonical registry files.

When should I avoid automatic extension registration in scope-routed registries?

Avoid automatic extension registration when canonical registry files are unavailable or schema validation cannot be enforced. The workflow requires integration with extension discovery pipelines and proper scope routing to prevent disconnected or invalid registry entries.