Skills extend-signal-schema
๐Ÿ“ฆ

extend-signal-schema

Content revision r2 Safe โš™๏ธ External commands

Extend AFI Signal Schemas Safely

Schema changes can break validators, consumers, and existing signal data. This skill guides scoped Zod schema updates with compatibility checks, deterministic validation, and focused tests.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "extend-signal-schema" from https://skillstore.io/skills/afi-protocol-extend-signal-schema.md and its manifest at https://skillstore.io/api/skills/afi-protocol-extend-signal-schema/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "extend-signal-schema". Add an optional macro regime field to Enriched signals.

Expected outcome:

  • Stage: Enriched.
  • Field: macro_regime, optional enum with risk_on, risk_off, and neutral.
  • Review the universal signal schema, type exports, and valid and invalid enum tests.
  • Compatibility: existing signals remain valid because the field is optional.

Using "extend-signal-schema". Make content required for all signals.

Expected outcome:

  • Scope: all signal stages.
  • This is a breaking contract change.
  • Compare an optional-first rollout, a temporary default, and an explicit data migration.
  • Request human approval before changing requiredness.

Security Audit

Safe
v9 โ€ข 7/20/2026 Open versioned report

All 63 static findings are false positives caused by Markdown backticks and ordinary documentation language. The skill provides schema-change guidance, limits scope, requires human clarification for unclear requests, and does not contain executable commands, network access, data collection, or prompt-injection text.

1
Files scanned
376
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: claude View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/afi-protocol-extend-signal-schema/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/afi-protocol-extend-signal-schema/security.svg)](https://skillstore.io/skills/afi-protocol-extend-signal-schema?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/afi-protocol-extend-signal-schema?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/afi-protocol-extend-signal-schema/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/afi-protocol-extend-signal-schema.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

AFI-Protocol. (2026). extend-signal-schema security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/afi-protocol-extend-signal-schema/audits/9

BibTeX citation

@techreport{afi-protocol-afi-protocol-extend-signal-schema-2026, author = {AFI-Protocol}, title = {extend-signal-schema security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/afi-protocol-extend-signal-schema/audits/9}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "extend-signal-schema security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "AFI-Protocol" date-released: "2026-07-20" url: "https://skillstore.io/skills/afi-protocol-extend-signal-schema/audits/9" identifiers: - type: other value: "skillstore:afi-protocol-extend-signal-schema:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance

What You Can Build

Add an optional enrichment field

Add a constrained optional field to an Enriched signal while preserving existing producers and consumers.

Plan a required-field migration

Evaluate optional-first, default-value, or explicit migration approaches before changing a shared signal contract.

Update validation coverage

Define valid, invalid, and optionality test cases for a schema field and its related validator behavior.

Try These Prompts

Add one optional field
Use extend-signal-schema to add an optional macro_regime field to Enriched signals. Allow risk_on, risk_off, and neutral. Identify affected files and tests.
Refine an enum
Use extend-signal-schema to extend the action enum for Scored signals with close and reduce. Preserve backwards compatibility and propose test cases.
Add a nested risk object
Use extend-signal-schema to add an optional risk_breakdown object to Scored signals. Define field types, validation rules, exports, migration effects, and tests.
Plan a breaking migration
Use extend-signal-schema to make content required across signal stages. Compare optional-first, defaults, and explicit migration. Stop for approval before any breaking change.

Best Practices

  • Restate lifecycle stage, field type, optionality, and migration impact before editing.
  • Add focused valid, invalid, and compatibility tests with every schema change.
  • Keep validators deterministic and document any approved exception.

Avoid

  • Do not add PoI or PoInsight fields to signal payloads.
  • Do not rename, remove, or tighten fields without a migration strategy and approval.
  • Do not extend the task into orchestration, token, gateway, or infrastructure repositories.

Frequently Asked Questions

Which signal stages does this skill cover?
It covers Raw, Enriched, Analyzed, and Scored signal schemas in afi-core.
Can it add a new Zod field?
Yes. It guides appropriate Zod types, enums, defaults, optionality, and validation constraints.
Does it support breaking schema changes?
It can plan them, but it requires a clear migration strategy and human approval.
Will it modify pipeline orchestration?
No. Pipeline composition belongs in afi-reactor and is outside this skill scope.
Can PoI or PoInsight become signal fields?
No. The skill keeps them as validator-level traits and escalates requests that violate this boundary.
Does it run builds and tests automatically?
It recommends relevant build and test commands. Results are only confirmed after they run in the target repository.

Developer Details

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

e6c11260b67d11d4944610e4044970c930ca27fd

Maintenance freshness

7/20/2026

Usage

6 downloads ยท 237 views

File structure

๐Ÿ“„ SKILL.md

View all