An agent skill pack: three skills that keep projects understood, in sync, and lean. Each skill is a self-contained folder in the Agent Skills format (SKILL.md, with references/ and scripts/ beside it), so it works in any agent that reads SKILL.md, and each works installed alone. Installed together, they can share state through a project's docs/PULSE.json; that is optional. Known until commit 19a8722 as Skills Trifecta.
| Skill | Alias | Role | Core question |
|---|---|---|---|
| DevCom5 | Logger | Docs, audit, comms | What does this project know about itself? |
| Synk182 | Symphonous Strategist | Agreement between two copies | Are the copies in agreement? |
| Solid8 | Denser / Shrinksmith | Consolidation | What can be unified without losing meaning? |
Versions: DevCom5 1.3 · Synk182 3.3 · Solid8 1.3 · Trifecta Protocol 3.0.
Optional protocol for shared state: docs/TRIFECTA.md
Copy any one of devcom5/, synk182/ and solid8/, or all three, into a skills folder your agent reads. The shared location comes first:
~/.agents/skills/for every project, or a project's own.agents/skills/for that project alone.
Or, with the skills.sh CLI:
npx skills add SPRIC76/The-TriadSome hosts read their own folder as well, or take an uploaded package. These are examples only, not a list of what is supported; any agent that reads SKILL.md folders can use the skills, from the folder its documentation names:
| Host (example) | Where the skill folders go |
|---|---|
| Codex | ~/.agents/skills/ or a repository's .agents/skills/ |
| Claude Code | ~/.claude/skills/ or a project's .claude/skills/ |
| Cursor | ~/.cursor/skills/ or a project's .cursor/skills/ |
| A host that takes uploads (claude.ai, for example) | Zip each skill folder as <name>.skill, with <name>/SKILL.md at its root, and upload it |
Requirements: Python 3.10+, optional, for synk182/scripts/synk_engine.py and solid8/scripts/denser_engine.py (standard library only). With no skill system at all, the workflow docs and the scripts still work by hand.
Badge snippet:
[](https://skills.sh/SPRIC76/The-Triad)Each skill works alone. Where more than one is installed, these orders suit most projects:
- All three: DevCom5 (Cartographer) → Synk182 → Solid8 → DevCom5 (Architect)
- Docs + lean: DevCom5 → Solid8 → DevCom5
- Docs + sync: DevCom5 (Cartographer) → Synk182 → DevCom5 (Architect)
- Sync + lean: Synk182 → Solid8
These skills guide an AI agent — they do not auto-run destructive actions.
- Synk182 and Solid8 require explicit user approval for merges and consolidation.
- Synk182's engine writes nothing until it applies plan items you approved, backs up each file first, refuses an item whose path leaves the copies or whose target changed since the plan was written, and never writes, backs up, restores or deletes through a junction or link.
- Archives are written under
[project]/ARCHIVE/before risky operations. - Review archives and proposals before deleting anything.
Far from the woods and a lager, look farther. One might never glimpse a forest through the trees, never stood tall, aye, they'd bend at their knees
Three modes: Cartographer (read/diagnose) · Architect (5-doc system) · Scribe (proposals, specs, internal comms).
Highlights:
- Adaptive depth: Pulse → Standard → Thorough → Deep (can shift mid-scan)
- Digest system via
docs/PULSE.json— read first, write last - Five-document framework in
/docs: INDEX, ARCHITECTURE, USER_EXPERIENCE, PLANNING, HISTORY - Maintains a project's existing documentation system instead of creating a parallel one
- Status:
📡 DevCom5: [staleness] | Depth: … | Docs: [n/5]
Triggers: devcom5, dc5, logger, documentation, project status, catch-up, README and changelog updates, proposals, updates on progress, plans and problems, newsletters, and more (see the description in devcom5/SKILL.md).
Not DevCom5: proving a change works or grading its evidence (a verification tool), a person's own knowledge base outside a project (a knowledge-search skill), rendering diagrams (a diagramming skill).
References: devcom5/references/ — audit protocol, universal template, comms formats.
Categorically and formally formulated to link between sink, sync, and Blink182
Highlights:
- Any two copies of a project: a sandbox or upload, a mounted or synced folder, a git worktree, another machine's copy, a deployed copy
- Similarity spectrum 0% to >100% with six-layer verification
- 60% merge threshold; mandatory review above 60%; supersets never auto-resolved
- Backs up every file before overwriting (
[project]/ARCHIVE/synk-[timestamp]/, with manifest and rollback notes), applies only approved items, and rolls back any copy that fails verification - Status:
🔄for scans, rigor shifts, completion
Not Synk: Single-file edits, in-directory moves, redundancy inside one copy (a consolidation tool), git branch merges (git), repo and worktree rules (your repository's own rules), what a version can do rather than what its files hold (a verification tool).
Script:
python synk182/scripts/synk_engine.py USER_COPY WORKING_COPY # dashboard, read-only
python synk182/scripts/synk_engine.py USER_COPY WORKING_COPY --plan plan.json # numbered plan, nothing written
python synk182/scripts/synk_engine.py USER_COPY WORKING_COPY --apply plan.json --approve 2,5Call me Denser if it's not getting through.
"Similar to a dancer phonetically, although I'm not a dancer. I do not dance, nor will I chance to lapse with you in proper trance."
Highlights:
- Tier S–D similarity pipeline; three laws (no delete without approval, lossless merge, archive first)
- Finds version (
_v2), copy (- Copy,(2)) and backup (.bak,.old) sprawl; compares Markdown by section, JSON by structure, binaries by hash; treats archive and staging folders as intentional, and never proposes a merge inside one - Solid8 = solid + ∞ rotated — tames endless project entropy
- Formerly Denser v1.0
- Status:
⚗️
Not Solid8: two copies of a project (a two-copy sync tool), vetting or absorbing an outside tool as your own (a tool-vetting workflow), memory notes (a memory-consolidation tool).
Script: python solid8/scripts/denser_engine.py <target_dir> [--details N] [--json proposal.json] (read-only analysis; archives before any change).
devcom5/ SKILL.md + references/
synk182/ SKILL.md + references/ + scripts/
solid8/ SKILL.md + references/ + scripts/
docs/ TRIFECTA.md
tests/ test_triad.py — kept tests for the engines, the skill folders and this pack (never shipped inside a skill);
the pack's own checks: every name-shaped token in its Markdown must be in a committed vocabulary,
no skill names another outside its optional integration section or frames itself for one host,
each skill works installed alone, and TRIAD_PRIVATE_NAMES may name a deny-list kept outside the repository
Run the tests from this folder: python -B -m unittest discover -s tests -v
See also: The Proof Pack, a separate pack for verifying changes.
Freeware — see LICENSE. Copyright (c) 2026 MK1 Enterprise. Free to download and use; please link to this repository rather than rehosting it. Versions up to commit 19a8722 were released under MIT and keep it.
The Triad · Freeware