aiception

Extract reusable operational knowledge from work sessions into structured SKILL.md definitions.

4.4k|856|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/NateBJones-Projects/OB1 --skill aiception-natebjones-projects
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aiception
Source: https://github.com/NateBJones-Projects/OB1/tree/main/skills/claudeception
Command: npx skills add https://github.com/NateBJones-Projects/OB1 --skill aiception-natebjones-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture non-obvious discoveries from work sessions and convert them into structured, reusable skills so valuable troubleshooting steps, error resolutions, and workflow optimizations are preserved and discoverable.

Core Features & Use Cases

  • Automated Extraction: Identify candidate learnings from debugging, misleading errors, tool integration quirks, and workflow improvements.
  • Skill Drafting & Structure: Format new skills with clear triggers, solutions, verification steps, examples, and references ready for saving as SKILL.md files.
  • Open Brain Integration: Check for duplicates via Open Brain, update or link existing skills, and capture new skills back into the knowledge store.
  • Use Case: After a 30-minute debugging session that uncovered a non-obvious fix, run a retrospective to generate a concise skill that triggers on the same error message or symptom.

Quick Start

Invoke /aiception at session end and ask the assistant to extract the top reusable findings and save them as SKILL.md entries to Open Brain.

Frequently Asked Questions about aiception

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

FAQPage Schema
How do I extract reusable knowledge from a debugging session?▼

You can capture session lessons by identifying non-obvious discoveries, misleading error resolutions, and workflow optimizations, then converting them into structured SKILL.md files for future reuse and discovery.

What is the best way to document non-obvious troubleshooting steps for future reuse?▼

The best way to document troubleshooting steps is running an end-of-session retrospective to generate a concise skill that triggers on the same error message or symptom for future reference.

Can I check for duplicate skills when capturing new workflow optimizations?▼

Checking for duplicates requires optional integration with Open Brain, which allows you to detect existing skills, update or link them, and capture new entries back into the knowledge store.

Do I need an AI client to save session lessons as reusable skills?▼

An AI client capable of loading reusable skills or prompts is required to extract findings from work sessions and save them as structured SKILL.md entries.

When should I run a retrospective to extract operational knowledge?▼

A retrospective to extract operational knowledge should be run during debugging, trial-and-error development, and at the end of sessions to identify non-obvious solutions and workflow improvements.