plugins/agentic-behavior/skills/claude-code/SKILL.md
Reference material for Claude Code internals — the on-disk layout under ~/.claude and project-scope .claude, the plugin cache, session-env propagation, and the full hook lifecycle. Auto-recall when working on Claude-Code-related tasks: writing or debugging hooks, authoring plugins, inspecting session state, troubleshooting why an env var is or isn't visible to a Bash tool call, or when paths under ~/.claude or ~/.claude/plugins/ come up.
npx skillsauth add nsheaps/ai-mktpl claude-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reference material for how Claude Code (the CLI harness) is laid out on disk and how its hook system works. This is auto-recalled when an agent needs to reason about Claude Code internals; the body here is intentionally short so it doesn't bloat context. Read the supplementary docs in this directory for detail when the task warrants it.
| Task | Doc |
| -------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| "Where does Claude store sessions / projects / plugins?" | folder-structure.md |
| "What's in ~/.claude/session-env/<id>/ and is it a leak?" | folder-structure.md (session-env section) |
| "How is project path encoded under ~/.claude/projects/?" | folder-structure.md |
| "What hook events exist? When does X fire?" | hooks.md |
| "What JSON does a PreToolUse hook receive / return?" | hooks.md |
| "Difference between command, prompt, agent, http, mcp_tool hook types" | hooks.md |
| "How do SessionStart hooks propagate env to Bash calls?" | hooks.md (CLAUDE_ENV_FILE section) |
~/.claude/ (shared across projects on this machine)<repo>/.claude/ (committed to the repo, project-specific)~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/settings.json under a top-level hooks key,
or bundled inside a plugin at <plugin>/hooks/hooks.json.plugin-dev:plugin-structure — authoring plugin manifests and layoutplugin-dev:hook-development — writing hooks (events, output contracts)plugin-dev:skill-development — authoring skills like this oneupdate-config — modifying settings.json / settings.local.jsonWhen this skill and the official docs disagree, the official docs win: https://code.claude.com/docs/en/hooks. File a follow-up to update this skill if you find a discrepancy.
development
Manage GitHub App installation tokens in Claude Code sessions. Use when tokens expire, auth errors occur in long-running sessions, or when setting up GitHub App credentials for agent teams. <example>my github token expired</example> <example>refresh the github app token</example> <example>check token status</example> <example>set up github app authentication for this session</example>
tools
Auto-detect project formatting tools and configure edit-utils settings
tools
Use this skill when the user asks about 1Password, secrets management, retrieving credentials, using op CLI, service accounts, secret references, vault operations, or any task involving the 1Password CLI (op). Also use when needing to inject secrets into environment variables, read passwords or API keys from 1Password, or manage 1Password items from the command line.
tools
Use this skill when the user asks about op-exec, running commands with 1Password secrets injected, wrapping processes with secret injection, automating secret-aware command execution, or configuring whole-item environment injection with multiple output targets. op-exec is a wrapper around the 1Password CLI that simplifies running commands with secrets from 1Password vaults.