synthos-probe

Validates structural integrity of Synthos cognitive atoms and benchmarks all SKILL.md files.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill synthos-probe-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthos-probe
Source: https://github.com/yakeworld/Synthos/tree/main/skills/extended/external-automation/automation-skills/maintenance/synthos-probe
Command: npx skills add https://github.com/yakeworld/Synthos --skill synthos-probe-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It detects structural decay in a large skill library by verifying that each core cognitive atom has a version, signature, and IO_CONTRACT, and by benchmarking every SKILL.md file for valid YAML frontmatter and git tracking. ## Core Features & Use Cases - 7-Atom Structural Check: Verifies has_version, has_signature, and has_io_contract for each core atom, computing a structural score as fully-passing atoms divided by 7. - Full Benchmark: Counts all SKILL.md files via os.walk (including ARCHIVED-SKILL.md variants), confirms git tracking with relative paths, and validates evolution-state.json parses. - Drift Self-Check: Runs a three-step green/yellow/red drift assessment before probing. - Use Case: Run a periodic maintenance audit to catch systemic gaps, such as 5 of 7 atoms missing signature and IO_CONTRACT, and output a line like SYNTHOS PROBE: structural=0.71, benchmark=1.00, drift=green. ## Quick Start Run a full structural probe of the Synthos repository's seven core atoms and benchmark all SKILL.md files, then report the structural score, benchmark score, and drift status.

Frequently Asked Questions about synthos-probe

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

FAQPage Schema
How do I check structural integrity of SKILL.md files?

Parse each SKILL.md frontmatter and verify three attributes: version (top-level or nested under metadata.synthos.version), an explicit signature declaration, and an IO_CONTRACT section. The structural score equals fully-passing atoms divided by the total atom count.

How to count all SKILL.md files in a repository accurately?

Use os.walk and match filenames containing SKILL.md rather than exact-name matching, so variants like ARCHIVED-SKILL.md are included. Never trust counts stated in specs; always derive the number from an actual filesystem traversal.

Why does signature detection give false positives in frontmatter?

Treating any name: field in frontmatter as a signature overstates results. Require an independent signature declaration or a name plus signature combination, otherwise a 0/7 result can be misreported as 6/7.

Why does the probe fail to find research-ideation?

research-ideation lives at skills/research/research-ideation/SKILL.md, not at the flat skills/research-ideation/ path. Always confirm the actual hierarchical path with os.path.exists before checking, and record missing atoms as 0/3 rather than skipping them.

Can I trust previous probe cycle results?

No. Each cycle must independently re-verify per-atom results because earlier runs used looser detection logic and overstated pass rates. Treat strict Cron-run detections as ground truth and flag discrepancies as corrected.