claudeception

Extract reusable debugging insights from conversation history into Markdown skill definitions.

4|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/k97/dock-tile --skill claudeception-k97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claudeception
Source: https://github.com/k97/dock-tile/tree/main/website/.claude/skills/claudeception
Command: npx skills add https://github.com/k97/dock-tile --skill claudeception-k97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the problem of losing valuable, non-obvious knowledge gained during complex debugging or task-solving sessions by codifying it into reusable skills.

Core Features & Use Cases

  • Autonomous Extraction: Automatically identifies and preserves reusable patterns, workarounds, and debugging insights from your conversation history.
  • Continuous Improvement: Enables the agent to build a library of specialized knowledge that grows more effective with every session.
  • Use Case: After spending hours debugging a tricky Next.js server-side error, use this skill to save the root cause and resolution steps so that future instances of the same error can be solved in seconds.

Quick Start

Invoke the claudeception skill at the end of a session to review your work and extract any valuable learnings into a new skill.

Frequently Asked Questions about claudeception

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract reusable debugging insights from my work sessions?

You can extract debugging insights by analyzing conversation history to identify non-obvious workarounds and structuring them into standardized Markdown skill definitions for future use.

What is the best way to save complex problem-solving workarounds for future use?

The best way to save complex workarounds is codifying them into persistent, actionable skill units that capture project-specific configurations and root causes for continuous learning.

Can I automatically capture debugging knowledge from project-specific configurations?

Yes, autonomous extraction automatically identifies and preserves reusable patterns and project-specific configurations from your conversation history to build a specialized knowledge library.

How do I create a persistent knowledge library from my debugging sessions?

Create a persistent knowledge library by invoking the extraction process at the end of a session to review work and save valuable learnings into new skill definitions.

When should I codify technical workarounds into standardized skill definitions?

Codify technical workarounds into skill definitions after spending significant time resolving tricky errors, to ensure future instances of the same error can be solved in seconds.

Does this skill extraction process require any specific dependencies or environments?

No specific dependencies are required, but the process needs the ability to analyze conversation history and structure findings into standardized Markdown skill definitions.