Receber por email
← Voltar para o catálogo

vault-health-feedback

Diagnose whether an Obsidian knowledge workflow produces cognitive return or is becoming a passive archive. Load when vault feels archival or dead. Do NOT use for inbox triage, link review, synthesis, or direct restructuring.

7estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add r007b34r/opencode-obsidian-knowledge-workflow

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/vault-health-feedback/svg)](https://www.skillteca.com.br/skills/vault-health-feedback)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

vault-health-feedback

Constraints

  • NEVER scan whole vault; sample strategically
  • NEVER give more than 3 recommendations
  • Check layers in order: workflow -> cognitive -> structural
  • NEVER equate structural mess with system failure (check workflow first)
  • NEVER repair, move, or restructure without explicit confirmation

Trigger Boundary

Use when: vault feels archival, knowledge not returning, system health diagnosis needed, highest-leverage repair unclear, user says "vault is d

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn