Agent skill

Claudeception

by divinevideo in divinevideo/divine-mobile

A skill your agent uses when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal

MITAuto-check passedDevelopment

Install Claudeception

skills CLI
$ npx skills add divinevideo/divine-mobile --skill claudeception -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install divinevideo/divine-mobile claudeception --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/claudeception .claude/skills/claudeception && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
claudeception
GitHub stars
266
Token cost
~1.1k tokens
SKILL.md length
632 words
Files
10 (incl. scripts)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal

  • Works in 6 steps: Review the task or session → Isolate the single learning worth… → Choose a dated filename with a concise… → …
  • Reviewing what was learned after debugging
  • SKILL.md covers When To Use, Core Rule, Capture Threshold and Output Location, plus 6 more sections
  • Runs Shell scripts from its folder

What it does

Claudeception is an agent skill from divinevideo/divine-mobile. Use when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts (for example `README.md`, `WARP.md` and `examples/2026-01-15-nextjs-server-side-error-debugging.md`).

It sits in Development, covering Accounting and bookkeeping and Debugging. The licence is MIT.

When your agent uses it

  • Reviewing what was learned after debugging
  • Workaround discovery
  • Trial-and-error investigation
  • Capture it as a dated journal entry under ~/.codex/journal

Example prompts

  • “/claudeception”

Requirements

  • A Bash shell

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Review the task or session
  2. Isolate the single learning worth preserving
  3. Choose a dated filename with a concise slug
  4. Write the journal entry using the template
  5. Include exact evidence and the real takeaway
  6. Stop after writing the entry

What it can do on your machine

Read from SKILL.md and the folder at commit 4c622be. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Claudeception loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 632 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from divinevideo/divine-mobile at commit 4c622be, republished under its MIT licence (© divinevideo). 632 words, ~1,132 tokens.

Download SKILL.mdSave it as .claude/skills/claudeception/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
claudeception
description
Use when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal

Claudeception

Claudeception captures episodic memory from work sessions.

It does not create or update skills. Its job is to preserve what happened, what was learned, and why it mattered in a dated journal entry that can be searched later or promoted through a separate workflow.

When To Use

Use this skill when any of these are true:

  • A task required non-obvious debugging or investigation
  • A workaround or recovery path was discovered through trial and error
  • An error message was misleading and the real root cause was learned
  • A project-specific or system-specific constraint was uncovered
  • The user asks /claudeception
  • The user says "save this as a skill", "extract a skill from this", or "what did we learn?"

Do not use this skill to create durable procedural knowledge. If the learning should become a reusable skill, leave that for a separate promotion step.

Core Rule

Never create a skill from this skill.

Even when the user says "save this as a skill", honor the intent by writing a journal entry unless they explicitly ask for a separate skill-writing workflow.

Capture Threshold

Write a journal entry when the session produced knowledge that is worth preserving, even if it is narrow or specific to one system.

Good journal material:

  • Incident-specific discoveries
  • System quirks and deployment gotchas
  • Root causes behind confusing failures
  • Investigated tradeoffs and workarounds
  • Repeated patterns that are not generalized yet

Skip capture when:

  • The task was a routine documentation lookup
  • The conclusion is already covered cleanly by an existing skill or project docs
  • The note would mostly restate obvious knowledge
  • The note would require storing secrets or sensitive internal details

Output Location

Write entries to:

~/.codex/journal/YYYY-MM-DD-topic-slug.md

Examples:

  • ~/.codex/journal/2026-04-05-fastly-draft-version-publish-mismatch.md
  • ~/.codex/journal/2026-04-05-nextjs-server-side-error-debugging.md

If multiple notes land on the same date with the same slug, add a short suffix.

Entry Format

Use the template in resources/journal-entry-template.md.

Every entry should include:

  • Frontmatter with date, title, tags, and source_trigger
  • A short factual description of what happened
  • The actual learning, not just the symptoms
  • Evidence such as errors, commands, files, or observations
  • A brief reuse signal describing whether this looks one-off or recurring

Keep the note concrete. Journal entries are not polished runbooks.

Show full SKILL.md (278 more words)Show less

Workflow

  1. Review the task or session
  2. Isolate the single learning worth preserving
  3. Choose a dated filename with a concise slug
  4. Write the journal entry using the template
  5. Include exact evidence and the real takeaway
  6. Stop after writing the entry

Do not create a new skill. Do not update an existing skill. Do not generalize beyond what the evidence supports.

Retrospective Mode

When /claudeception is invoked at the end of a session:

  1. Review the session for journal-worthy learnings
  2. Prefer one focused entry per distinct incident or discovery
  3. If there are multiple unrelated learnings, write separate entries
  4. Summarize what was captured and where it was written

Quality Gates

Before finalizing a journal entry, verify:

  • The filename is dated
  • The note describes something actually observed or verified
  • The writeup includes evidence or concrete trigger conditions
  • The note preserves local context instead of inflating it into a general skill
  • No secrets, credentials, or sensitive URLs are included
  • No new skill files were created

Anti-Patterns

  • Turning every discovery into a reusable skill
  • Rewriting the note as a polished runbook
  • Stripping away the concrete system context that made the discovery useful
  • Capturing vague conclusions without evidence
  • Creating duplicate journal entries for the same learning in the same session

Self-Check Prompts

Ask:

  • What happened that was not obvious at the start?
  • What was the actual root cause or constraint?
  • What would future-me want to grep for?
  • Is this a concrete incident note or a reusable procedure?

If it is an incident note, write it to the journal.

If it is a reusable procedure, do not create it here. Leave it for a separate promotion workflow.

© divinevideo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts) in .agents/skills/claudeception of divinevideo/divine-mobile.

  • SKILL.md
  • LICENSE
  • README.md
  • WARP.md
  • examples/2026-01-15-nextjs-server-side-error-debugging.md
  • examples/2026-01-16-prisma-connection-pool-exhaustion.md
  • examples/2026-01-17-typescript-circular-dependency.md
  • resources/journal-entry-template.md
  • resources/research-references.md
  • scripts/claudeception-activator.sh

Open the folder on GitHubat commit 4c622be

Compare with similar skills

Claudeception next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Claudeception compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Claudeception this skilldivinevideo/divine-mobile266—~1.1kAutomated safety check: PassMIT
QA Find Bugs CLIbex-co/beancount-io295—~2.2kAutomated safety check: NotesMIT
Sandbox Lifecycle Debugvercel-labs/vercel-openclaw-archived117—~809Automated safety check: PassMIT
Debugging Cockroachdb Operator Migrationscockroachdb/helm-charts105—~3.6kAutomated safety check: PassApache-2.0
Gh QueueLanternOps/breeze131—~5kAutomated safety check: PassAGPL-3.0
Profiler Enable ModuleIvanMurzak/Unity-MCP4.4k1 repos~557Automated safety check: PassApache-2.0

Similar skills

  • QA Find Bugs CLI

    bex-co/beancount-io

    Hunt bugs in the Beancount.io bea CLI by running real commands against isolated synthetic ledgers, checking output and file effects, reproducing failures, tracing root causes, and deduplicating…

    295 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check: notes
  • Sandbox Lifecycle Debug

    vercel-labs/vercel-openclaw-archived

    Official

    Sandbox lifecycle debugging for vercel-openclaw: create, resume, stop, snapshotting, reset, stale-running reconciliation, persistent Sandbox v2 behavior, hot spares, and lifecycle locks.

    117 GitHub stars~809 tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration.

    105 GitHub stars~3.6k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed
  • Gh Queue

    LanternOps/breeze

    A skill your agent uses when reviewing, triaging, or managing the incoming GitHub backlog on the Breeze repo — PRs, Discussions, AND Issues.

    131 GitHub stars~5k tokensUpdated today
    DevelopmentAuto-check passed
  • Profiler Enable Module

    IvanMurzak/Unity-MCP

    Toggle the wrapper's local 'enabled' flag for a named profiler module.

    4.4k GitHub starsUsed in 1 repo~557 tokens
    DevelopmentAuto-check passed
  • Profiler List Modules

    IvanMurzak/Unity-MCP

    List all known profiler module names with their local 'enabled' bookkeeping flag.

    4.4k GitHub starsUsed in 1 repo~776 tokens
    DevelopmentAuto-check passed

More from divinevideo/divine-mobile

All 103 skills in this repo
  • Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y".

    266 GitHub stars~931 tokensUpdated today
    Auto-check passed
  • Art Direct

    divinevideo/divine-mobile

    Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language.

    266 GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Async Await Null Race Condition

    divinevideo/divine-mobile

    Fix "Null check operator used on a null value" errors when an object is set to null during an async await.

    266 GitHub stars~881 tokensUpdated today
    Auto-check passed
  • AWS V4 Signing Custom Headers Gcs

    divinevideo/divine-mobile

    Add custom metadata headers (x-amz-meta-) to AWS v4 signed requests for GCS S3-compatible API.

    266 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Bash Herestring Newline Secrets

    divinevideo/divine-mobile

    Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings.

    266 GitHub stars~791 tokensUpdated today
    Auto-check passed
  • Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp).

    266 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Questions about Claudeception

What does Claudeception do?

A skill your agent uses when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal. Claudeception is an agent skill from divinevideo/divine-mobile.

When should I use Claudeception?

Claudeception fits situations like: reviewing what was learned after debugging; workaround discovery; trial-and-error investigation; capture it as a dated journal entry under ~/.codex/journal.

How do I install Claudeception in Claude Code?

Run `npx skills add divinevideo/divine-mobile --skill claudeception -a claude-code`. Or copy the skill folder (.agents/skills/claudeception in divinevideo/divine-mobile) into .claude/skills/claudeception in your project. Claude Code loads it when a task matches its description.

How do I install Claudeception in Codex?

Run `npx skills add divinevideo/divine-mobile --skill claudeception -a codex`. Or copy the skill folder (.agents/skills/claudeception in divinevideo/divine-mobile) into .agents/skills/claudeception in your project. Codex loads it when a task matches its description.

Can I use Claudeception in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add divinevideo/divine-mobile --skill claudeception -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claudeception, .gemini/skills/claudeception, .github/skills/claudeception and .opencode/skills/claudeception in your project.

What does Claudeception need to run?

Going by SKILL.md and its folder, Claudeception needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Claudeception access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Claudeception safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Claudeception use?

Claudeception is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Claudeception use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Claudeception?

Skills that share tags, products or a category with Claudeception: QA Find Bugs CLI (bex-co/beancount-io, 295 stars), Sandbox Lifecycle Debug (vercel-labs/vercel-openclaw-archived, 117 stars), Debugging Cockroachdb Operator Migrations (cockroachdb/helm-charts, 105 stars) and Gh Queue (LanternOps/breeze, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Claudeception?

divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 266 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 8, 2026.

Source: divinevideo/divine-mobile on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.