Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 42 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,19 @@ This skill fixes that. When Claude Code discovers something non-obvious (a debug

### Step 1: Clone the skill

**User-level (recommended)**
**Linux/Mac (user-level, recommended)**

```bash
git clone https://github.com/blader/Claudeception.git ~/.claude/skills/claudeception
```

**Project-level**
**Windows (PowerShell)**

```powershell
git clone https://github.com/blader/Claudeception.git "$env:USERPROFILE\.claude\skills\claudeception"
```

**Project-level (any platform)**

```bash
git clone https://github.com/blader/Claudeception.git .claude/skills/claudeception
Expand All @@ -24,6 +30,8 @@ git clone https://github.com/blader/Claudeception.git .claude/skills/claudecepti

The skill can activate via semantic matching, but a hook ensures it evaluates every session for extractable knowledge.

#### Linux/Mac

1. Create the hooks directory and copy the script:

```bash
Expand Down Expand Up @@ -51,6 +59,38 @@ chmod +x ~/.claude/hooks/claudeception-activator.sh
}
```

#### Windows

The bash script doesn't work on Windows. Use the Node.js version instead:

1. Create the hooks directory and copy the script (PowerShell):

```powershell
mkdir -Force "$env:USERPROFILE\.claude\hooks"
cp "$env:USERPROFILE\.claude\skills\claudeception\scripts\claudeception-activator.js" "$env:USERPROFILE\.claude\hooks\"
```

2. Add the hook to your Claude settings (`%USERPROFILE%\.claude\settings.json`):

```json
{
"hooks": {
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "node %USERPROFILE%\\.claude\\hooks\\claudeception-activator.js"
}
]
}
]
}
}
```

---

If you already have a `settings.json`, merge the `hooks` configuration into it.

The hook injects a reminder on every prompt that tells Claude to evaluate whether the current task produced extractable knowledge. This achieves higher activation rates than relying on semantic description matching alone.
Expand Down
36 changes: 36 additions & 0 deletions scripts/claudeception-activator.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
#!/usr/bin/env node

// Claudeception Auto-Activation Hook
// This hook ensures the claudeception skill evaluates every interaction
// for extractable knowledge worth preserving.
//
// Installation:
// 1. Copy this script to ~/.claude/hooks/
// 2. Add to ~/.claude/settings.json (see README for details)

console.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🧠 MANDATORY SKILL EVALUATION REQUIRED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

CRITICAL: After completing this user request, you MUST evaluate whether
it produced extractable knowledge using the claudeception skill.

EVALUATION PROTOCOL (NON-NEGOTIABLE):

1. COMPLETE the user's request first
2. EVALUATE: Ask yourself:
- Did this require non-obvious investigation or debugging?
- Was the solution something that would help in future similar situations?
- Did I discover something not immediately obvious from documentation?

3. IF YES to any question above:
ACTIVATE: Use Skill(claudeception) NOW to extract the knowledge

4. IF NO to all questions:
SKIP: No skill extraction needed

This is NOT optional. Failing to evaluate means valuable knowledge is lost.
The claudeception skill will decide whether to actually create a new
skill based on its quality criteria.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`);