triforce-sync-check
Verify skill sync across platforms
Skills may become inconsistent when copied across platforms. This skill validates that all skill files match between .public/skills, .codex/skills, and .claude/skills directories. Use before commits or in CI pipelines to catch drift early.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "triforce-sync-check". Run a complete triforce sync check on the skill directories
Resultado esperado:
- Count Check: PASS (15 skills in each directory)
- Structure Check: PASS (identical directory listings)
- Content Check: PASS (all hashes match)
- YAML Validation: PASS (all skills have name and description)
- Duplicate Check: PASS (no duplicate names)
- Result: All checks passed
A utilizar "triforce-sync-check". Compare directory structures between platforms
Resultado esperado:
- Comparing .public/skills with .codex/skills:
- No differences found - all directories match
- Comparing .public/skills with .claude/skills:
- No differences found - all directories match
A utilizar "triforce-sync-check". Validate YAML fields in all skills
Resultado esperado:
- Checking SKILL.md frontmatter in all skills...
- All 15 skills have valid name and description fields
- YAML validation: PASS
Auditoria de Segurança
SeguroDocumentation-only skill containing verification procedures. No executable code present. All operations are read-only filesystem checks using standard utilities (ls, diff, find, grep, md5). Shell commands shown are examples in documentation, not runtime execution. This is a reference guide for skill synchronization verification.
Fatores de risco
🌐 Acesso à rede (1)
📁 Acesso ao sistema de arquivos (1)
⚙️ Comandos externos (38)
Pontuação de qualidade
O Que Você Pode Construir
CI Pipeline Validation
Add to GitHub Actions workflows to block commits with desynchronized skills
Pre-commit Verification
Check skill consistency before pushing changes to ensure mirrors stay in sync
Deployment Check
Validate all skills are properly mirrored before production deployments
Tente Estes Prompts
Count the skills in .public/skills, .codex/skills, and .claude/skills. Report whether all three counts match.
Compare the directory structure of .public/skills with .codex/skills and .claude/skills. List any missing or extra directories.
Verify that all SKILL.md files have matching content hashes across .public/skills, .codex/skills, and .claude/skills. Report any mismatches.
Run a complete triforce sync check: verify counts match, structures match, content hashes match, YAML is valid, and no duplicate skill names exist. Provide a pass/fail summary.
Melhores Práticas
- Run the sync check before every commit that modifies skills
- Integrate into CI pipelines to catch drift automatically
- Fix issues at the SSOT (.public/skills) first, then sync
Evitar
- Manually editing mirrored directories instead of using sync
- Skipping verification after bulk skill changes
- Ignoring count mismatches without investigating the cause
Perguntas Frequentes
Which AI platforms are supported?
What are the sync limits?
How do I integrate with CI/CD?
Is my data safe?
What if checks fail?
How is this different from manual diff?
Detalhes do Desenvolvedor
Estrutura de arquivos
📄 SKILL.md