Agent skill · software engineering · aiskillstore
extend-signal-schema
Safely extend or refine AFI signal schemas and closely-related validators in afi-core, while preserving determinism, respecting PoI/PoInsight design, and obeying the AFI Droid Charter and AFI Core AGENTS.md boundaries.
Why this skill is useful
Provides specific guidelines and validation rules for extending signal schemas in afi-core that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Skill: extend-signal-schema (afi-core) Purpose Use this skill when you need to extend or refine signal schemas in afi-core, adding new fields or validation rules to the Raw, Enriched, Analyzed, or Scored signal schemas. This skill ensures changes are: Safe: Backwards compatible where possible, with clear migration paths Governed: Aligned with AFI Droid Charter, AFI Droid Playbook, and afi-core/AGENTS.md Correct: PoI/PoInsight remain validator-level traits, NOT signal fields Tested: Schema changes include minimal test coverage This skill is primarily used by schema-validator-droid and any future afi-core droids that work on signal schemas and validators. --- Preconditions Before changing anything, you MUST: 1. Read: afi-core/AGENTS.md AFI Droid Charter AFI Droid Playbook Target schema file(s) in schemas/ 2. Confirm: The requested change belongs in afi-core (signal language/validation), not in afi-reactor (orchestration) or afi-token (economics). The change does not introduce PoI/PoInsight as signal fields. The change does not require editing smart contracts, Eliza configs, or deployment/infra repos. If any requirement is unclear or appears to violate AGENTS.md or Charter, STOP and ask for human clarification instead of trying to be clever. --- Inputs Expected The caller should provide, in natural language or structured form: Target lifecycle stage: Raw, Enriched, Analyzed, or Scored Field name(s): The field(s) to add or refine Type/shape: e.g., string, number, enum, object, array Optionality: Required or optional? If optional, what's the default? Description: Brief explanation of field meaning and usage Backwards compatibility: Any migration concerns or breaking changes? If any of this information is missing, ask clarifying questions or produce a minimal, clearly-labeled stub with TODOs and conservative defaults. --- Step-by-Step Instructions When this skill is invoked, follow this sequence: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/extend-signal-schema