agentsclimarketplace

Synk182

Skill SPRIC76/skills-trifecta/synk182

Cursor agent skills: DevCom5, Synk182, Solid8 β€” the documentation, sync, and consolidation trifecta.

Install
npx -y skills add SPRIC76/skills-trifecta --skill synk182

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Intelligent multi-layer file synchronization between user's project directory and Claude's working environment. Handles 0% to >100% similarity: auto-sync for identical, intelligent merge for 60-99%, ultra-careful handling for superset/subset. Six-layer verification, three-tier backup, auto-rollback. Multi-tier adaptive depth (adjusts rigor during scan based on findings). Cross-skill integration with DevCom5 and Solid8 via PULSE.json. Standalone; amplified with DevCom5 / Solid8.

SKILL.md

5.4 KB, as published. Nobody here has run it

Synk182 β€” The Symphonous Strategist

Formerly nothing

*Formally a link between sink, and sync. "Who thinks this shi don't stink? let that sync in" signed- A. Blinken.

Bidirectional file sync with surgical precision, paranoid safety, and adaptive depth that adjusts mid-operation.

TRIGGER when/user mentions: "synk", "s182", "synk it", "synk files", syncing files, file discrepancies, "sync my project", "files are different", "push/pull files", or cross-skill signals indicate environment drift.

Immutable Corrections (User-Specified)

  1. Mandatory review for >60% similar (only 100% hash match skips review)
  2. 60% threshold for intelligent merge (not 75%)
  3. 100% superset/subset = ultra-careful handling, maximum scrutiny

Triggers

LevelPhrasesAction
🟒 Immediate"sync my project/files", "synchronize", "keep in sync"Activate
🟑 Confirm"update my project files"Clarify: Synk or direct edits?
πŸ”΄ Clarify"files are different", "don't see my file"Offer Synk
❌ Not SynkCreate/edit single files, move within dir, redundancy (β†’ Solid8)β€”

Similarity Spectrum

RangeRelationshipActionReview
>100%Superset/subsetUltra-careful merge⚠️ MAXIMUM
100%Identical (hash)Auto-syncNone (only case)
60-99%High similarityIntelligent mergeMandatory
<60%Low similarityManual/skipVariable

Six-Layer Verification

#LayerCatches
1ExistenceMissing files, deletions
2Hash (SHA-256)Any content change β€” gatekeeper: match = skip 3-6
3SizeTruncation, corruption
4TimestampStale versions
5Line countPartial writes
6Content diffSpecific changes

Three-Tier Adaptive Depth

Tier 1: Baseline from PULSE

ConditionRigor
synk_last_run < 24h, no signalsQuick β€” hash check only, skip unchanged
1-7 days or minor signalsStandard β€” full six-layer on all files
>7 days or drift signalsThorough β€” six-layer + relationship analysis + merge candidates

Tier 2: Adaptive Mid-Scan

Downshift: Quick scan finds 95%+ identical β†’ summary report, skip detailed diff. Upshift: Quick scan finds >10 non-identical files β†’ escalate to Thorough. Standard scan finds superset relationships β†’ escalate to Thorough for those clusters.

Report shifts: πŸ”„ Rigor adjusted: Quick β†’ Standard (15 files differ)

Tier 3: Cross-Skill Signals

drift_detected from DevCom5 β†’ β‰₯ Standard. consolidation_complete from Solid8 β†’ new baseline, full comparison. stale_project from DevCom5 β†’ Thorough.

Safety

Three-tier backup: Full project β†’ per-file β†’ incremental checkpoints. Auto-rollback: On any verification failure post-operation. Archive: [project]/ARCHIVE/synk-[timestamp]/ with manifest.json, originals, rollback.md.

Workflow

  1. Inventory β€” Scan both environments, fingerprint all files
  2. Compare β€” Classify by tier + direction (with adaptive depth adjustment)
  3. Propose β€” Dashboard: πŸ”„ βœ“12 identical | ⚠️2 superset | πŸ”€3 merge | βž•3 new
  4. Execute β€” After approval: backup β†’ sync/merge β†’ verify (six layers) β†’ log
  5. Report β€” πŸ”„ Synced: [n] | Verified: βœ“ | Archive: [path]

Scripts

scripts/synk_engine.py β€” Core synchronization engine:

  • SynkEngine class for bidirectional file sync
  • SHA-256 fingerprinting and six-layer verification
  • Similarity calculation with configurable thresholds
  • Merge proposal generation with conflict detection
  • Archive creation with manifest and rollback support

Merge Strategies

Standard (60-99%): Shared base β†’ user-unique + working-unique β†’ merged β†’ diff for review. Superset (>100%): Identify superset β†’ identify delta β†’ assess intent β†’ present with preview β†’ never auto-resolve. Configs (JSON/YAML): Structural key-value diff β†’ user version as authority.

Trifecta Signals

Full protocol: references/TRIFECTA_PROTOCOL.md

Emits: sync_completed β†’ DevCom5 | sync_conflict β†’ DevCom5 | environment_diverged β†’ DevCom5 | new_files_synced β†’ Solid8 Consumes: drift_detected (DevCom5) β†’ ↑rigor | consolidation_complete (Solid8) β†’ new baseline | stale_project (DevCom5) β†’ Thorough PULSE writes: synk_last_run, synk_drift_detected, synk_files_changed

Anti-Patterns

  • Syncing build artifacts (node_modules, bin/, obj/)
  • Auto-resolving superset merges
  • Syncing mid-edit (verify saved first)
  • Assuming newer = better
  • Consolidating during sync (Solid8's job)
  • Skipping verification layers

⁰ Formerly: unnamed sync utility (pre-v1) β†’ Synk v1.0 β†’ v2.0 β†’ Synk v3.0. Synk has no prior alias. It has always been Synk. That's the joke.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.