/ Directorio / Playground / raw-clauding-skills
● Comunidad lsnackerman ⚡ Instantáneo

raw-clauding-skills

por lsnackerman · lsnackerman/raw-clauding-skills

Eight workflow files for compound thinking with Claude — /session, /wrap, /pickup, /heartbeat — treat the AI as a persistent thought partner.

lsnackerman/raw-clauding-skills is a collection of slash-command workflows grounded in a year of daily AI collaboration. Core progression: /session (start a thinking thread) → /wrap (intentional closure) → /pickup (continuity next session) → /heartbeat (scan for emerging connections). Philosophy: 'Skills are files. Each one is a repeatable workflow you share with your AI'. Not a productivity hack pack — closer to a personal-practice toolkit.

Por qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

raw-clauding-skill.replay ▶ listo
0/0

Instalación

Repositorio del autor · Documentación oficial de Skills de Claude

Casos de uso

Usos del mundo real: raw-clauding-skills

Explore a complex question across multiple sessions without losing the thread

👤 Writers, researchers, strategists using AI for open-ended thinking ⏱ ~60 min beginner

Cuándo usarlo: You're circling a hard question and a single conversation isn't enough.

Flujo
  1. Open with /session
    /session — I want to think through what 'quality' means for our product.✓ Copiado
    → Claude frames the session with context scaffolding, not an immediate answer
  2. Work, then /wrap
    /wrap — capture what we landed on and what's still open.✓ Copiado
    → Concise closure doc with open threads noted
  3. Next day: /pickup
    /pickup from yesterday's session.✓ Copiado
    → Claude re-enters with your prior frame intact
  4. Weekly: /heartbeat
    /heartbeat — what's been recurring across the last 5 sessions?✓ Copiado
    → Patterns surfaced that you didn't notice inside a single session

Resultado: A sustained line of thinking that actually compounds, rather than restarts.

Errores comunes
  • Using /session for one-shot queries — Drop it for trivial questions — compound thinking has overhead

End a long project with a proper /wrap so you can return to it cleanly

👤 Solo operators leaving a project paused ⏱ ~10 min beginner

Cuándo usarlo: You're stepping away from something unfinished and want future-you to pick it up cleanly.

Flujo
  1. Run /wrap
    /wrap — capture state, open questions, and the one thing future-me needs to remember first.✓ Copiado
    → Doc written with an explicit re-entry note

Resultado: A re-entry doc that beats reading your own notes cold.

Combinar con: filesystem

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

raw-clauding-skill + planning-with-files

Use planning-with-files for disk-based state; raw-clauding for thinking structure on top

Combine: /session with planning-with-files writing findings.md as we go.✓ Copiado
raw-clauding-skill + filesystem

Persist /wrap and /pickup docs into your own journal

Save every /wrap output to ~/journal/sessions/.✓ Copiado

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
/session question or topic Open-ended thinking work worth preserving 0
/wrap current session End of a session you'll return to 0
/pickup prior session reference Resuming work 0
/heartbeat range (last N sessions) Periodically to catch what you didn't notice 0

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
None
Tokens por llamada
Modest — workflows are compact
Monetario
Free — skills are local files
Consejo
Don't run /heartbeat on every interaction; it earns its keep weekly.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials — pure prompts
Salida de datos: None

Resolución de problemas

Errores comunes y soluciones

Wrong trigger keywords — /pickup without prior /wrap loses context

Make sure your prior session actually ended in /wrap; otherwise pickup has nothing to anchor to.

Alternativas

raw-clauding-skills vs otros

AlternativaCuándo usarlaContrapartida
planning-with-filesYou want disk-based memory rather than thinking structureComplementary — different axes
Raw journalingYou prefer writing in a notebook appNo AI continuity between sessions

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills