/ Directory / Playground / raw-clauding-skills
● Community lsnackerman ⚡ Instant

raw-clauding-skills

by 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.

Why use it

Key features

Live Demo

What it looks like in practice

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

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "raw-clauding-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lsnackerman/raw-clauding-skills",
        "~/.claude/skills/raw-clauding-skills"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "raw-clauding-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lsnackerman/raw-clauding-skills",
        "~/.claude/skills/raw-clauding-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "raw-clauding-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lsnackerman/raw-clauding-skills",
        "~/.claude/skills/raw-clauding-skills"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "raw-clauding-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lsnackerman/raw-clauding-skills",
        "~/.claude/skills/raw-clauding-skills"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "raw-clauding-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/lsnackerman/raw-clauding-skills",
        "~/.claude/skills/raw-clauding-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "raw-clauding-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/lsnackerman/raw-clauding-skills",
          "~/.claude/skills/raw-clauding-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add raw-clauding-skill -- git clone https://github.com/lsnackerman/raw-clauding-skills ~/.claude/skills/raw-clauding-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use 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

When to use: You're circling a hard question and a single conversation isn't enough.

Prerequisites
  • Skill cloned — git clone https://github.com/lsnackerman/raw-clauding-skills ~/.claude/skills/raw-clauding-skills
Flow
  1. Open with /session
    /session — I want to think through what 'quality' means for our product.✓ Copied
    → 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.✓ Copied
    → Concise closure doc with open threads noted
  3. Next day: /pickup
    /pickup from yesterday's session.✓ Copied
    → Claude re-enters with your prior frame intact
  4. Weekly: /heartbeat
    /heartbeat — what's been recurring across the last 5 sessions?✓ Copied
    → Patterns surfaced that you didn't notice inside a single session

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

Pitfalls
  • 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

When to use: You're stepping away from something unfinished and want future-you to pick it up cleanly.

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

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

Combine with: filesystem

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied
raw-clauding-skill + filesystem

Persist /wrap and /pickup docs into your own journal

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

Tools

What this MCP exposes

ToolInputsWhen to callCost
/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

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Modest — workflows are compact
Monetary
Free — skills are local files
Tip
Don't run /heartbeat on every interaction; it earns its keep weekly.

Security

Permissions, secrets, blast radius

Credential storage: No credentials — pure prompts
Data egress: None

Troubleshooting

Common errors and fixes

Skill not invoked — Claude treats /session as a literal command it doesn't recognize

Make sure the skill is installed; if needed, paraphrase: 'use the raw-clauding /session workflow'.

Verify: ls ~/.claude/skills/raw-clauding-skills/SKILL.md
SKILL.md frontmatter wrong

Re-clone; description drives activation.

Verify: head ~/.claude/skills/raw-clauding-skills/SKILL.md
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.

Alternatives

raw-clauding-skills vs others

AlternativeWhen to use it insteadTradeoff
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

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills