- Home
- Skills
- Blader
- Claudeception
- Claudeception
claudeception_skill
- Shell
1.8k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill blader/claudeception --skill claudeception- LICENSE1.0 KB
- README.md6.0 KB
- SKILL.md14.7 KB
Overview
This skill automates continuous learning by extracting reusable knowledge from work sessions and codifying it into new Claude Code skills. It detects non-obvious solutions, error resolutions, and workflow optimizations, then creates or updates skills so the system improves over time. Use it to turn ad-hoc discoveries into reliable, searchable guidance.
How this skill works
Claudeception monitors sessions and evaluates whether recent work contains reusable insights. When triggered manually or after non-trivial debugging or trial-and-error, it analyzes the problem, verifies solutions, checks for existing skills, and either updates an existing skill or creates a new one with clear trigger conditions, steps, and verification. It records versioning, cross-references related skills, and includes references when web research was performed.
When to use it
- After solving a problem that required investigation or non-obvious debugging (>10 minutes)
- When a workaround, project-specific configuration, or integration trick is discovered
- If an error message was misleading and the real root cause was identified
- When a multi-step workflow can be simplified or standardized
- On explicit commands: "/claudeception", "save this as a skill", or "what did we learn?"
Best practices
- Be selective: only extract knowledge that is reusable, non-trivial, and verified
- Search existing skills first and update instead of duplicating when appropriate
- Document exact trigger conditions (error text, file names, environment) for discovery
- Include verification steps and examples so others can reproduce the fix
- Version skills: patch for wording, minor for new scenarios, major for breaking changes
Example use cases
- Discovering a Next.js server-side debugging pattern and saving it as a skill
- Extracting a workaround for a library bug that required a specific config tweak
- Saving a multi-step deployment optimization discovered during a release
- Recording the root cause and fix for a misleading CI error message
- Consolidating repeated ad-hoc fixes into a single reusable troubleshooting skill
FAQ
It searches existing skills by keywords, triggers, and exact error messages. Create new if no close match exists or if the root cause differs; update if same trigger and same fix or if the new content is a variant that fits the existing skill.
Should I always run web research before saving a skill?
Not always. Research when the topic involves external tools, best practices, or could be outdated. Skip research for project-specific, internal patterns that are unique to this codebase.