[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79QSN68HHX2739Z2VCXM89T":3,"skill-same:01M79QSN68HHX2739Z2VCXM89T":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79QSN68HHX2739Z2VCXM89T","session-detail",null,"Shows detailed information about a Claude Code session, including a session summary, associated tasks, and conversation messages (token\u002Fmodel\u002Ftool usage shown as a brief part of this overview). Use when the user says \"show session\", \"session details\", \"what happened in session X\". For a dedicated token-usage\u002Fcost\u002Fmodel breakdown only, use session-stats instead. If the session is only described by topic\u002Fcontent and not yet identified, use session-search first.","AndreHahm\u002Fandres-cc-marketplace","AndreHahm","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80748019?v=4","01M79N2VZJT9MAJ7K695C9VXQ4","01M79N2W06PFX8BSCQ592M8K8K",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-kit\u002Fskills\u002Fsession-detail\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: session-detail\ndescription: >-\n  Shows detailed information about a Claude Code session, including a session\n  summary, associated tasks, and conversation messages (token\u002Fmodel\u002Ftool usage\n  shown as a brief part of this overview). Use when the user says \"show\n  session\", \"session details\", \"what happened in session X\". For a dedicated\n  token-usage\u002Fcost\u002Fmodel breakdown only, use session-stats instead. If the session is only described\n  by topic\u002Fcontent and not yet identified, use session-search first.\nallowed-tools: Bash(python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_store.py\":*) Bash(python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\":*)\n---\n\n# Session Detail\n\nShow comprehensive details about a single session.\n\n## When to Use\n\n- Wants the full picture of one session: summary, tasks, and message transcript\n- \"show session\", \"session details\", \"what happened in session X\"\n\n## When NOT to Use\n\n- A dedicated token-usage\u002Fcost\u002Fmodel breakdown only, not the full profile → use `session-stats` instead\n- Cross-session task aggregation → use `session-tasks` instead\n- The target session isn't yet identified — described by content\u002Ftopic rather than an ID or clear\n  reference (e.g. \"what happened in the session where I fixed the login bug\") → use `session-search`\n  first to locate it; use `session-detail` once a specific session is identified.\n- Wants a portable recovery document for a *different* session, not live detail here → use\n  `session-resume` instead.\n- Wants a comparison between two sessions, not detail on one → use `session-diff` instead.\n- Wants only a bare chronological, event-by-event timeline for one session (no summary or task\n  context) → use `session-timeline`'s single-session mode (its Step 1, Option B) instead.\n- Wants a file\u002Ftranscript export, not detail shown in the conversation → use `session-export` instead.\n\n## Step 1: Get session detail\n\nIf no session ID is given, resolve the live session directly (safe even when the current working\ndirectory doesn't match where the session actually started — e.g. a worktree created mid-session):\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_store.py\" current\n```\n\nOtherwise:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_store.py\" session-detail \u003Csession-id>\n```\n\nThis returns: session summary (including the `path` field), token usage (input\u002Foutput\u002Fcache), models used, tools called, and associated task lists with their tasks. This command always prints JSON — no `--format` flag needed.\n\n## Step 2: Present summary\n\nShow a formatted summary:\n\n- **Session**: ID, project, date, duration\n- **Tokens**: input, output, cache read, cache create\n- **Models**: which models were used and how many turns each\n- **Tools**: top tools used with counts\n- **Tasks**: associated task lists and task status summary\n\n## Note on resumed sessions\n\nIf `is_resumed` is true in the stats, this session was started via `claude --resume` or `claude --continue`. The JSONL only contains messages from the resumed portion — earlier context from the parent session is not included. Mention this to the user so they understand why the transcript may appear to start mid-conversation.\n\n## Step 3: Show messages (optional)\n\nIf the user wants to see the conversation, use the `path` field from Step 1's `session` object:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\" messages \u003Csession-path> --limit 20\n```\n\nFor more messages, increase `--offset` and `--limit`:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\" messages \u003Csession-path> --offset 20 --limit 20\n```\n\nTo include tool call details:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\" messages \u003Csession-path> --include-tools --limit 20\n```\n\n## Testing & Validation\n\nEval suite: `evals\u002Fsession-detail\u002F` — 3 scenarios, `skill-tester` Quick Workflow blind comparison, all\npassed. Eval 3 verified a cross-session task query correctly redirects to `session-tasks` instead of\nbeing answered directly.\n\n**Last dated run record:** `evals\u002Fsession-detail\u002Fworkspace\u002Fiteration-2\u002Feval-{1,2,3}\u002Fwith_skill\u002Fgrading.json`,\n2026-09-03. `scripts\u002Fsmoke_test.py` structural self-check also passing as of the same date.\n\n**Verify this skill activates on:**\n- \"show session details for X\"\n- \"what happened in session X\"\n- \"give me the full picture of this session\"\n\n**Verify it does NOT activate on:**\n- \"how many tokens did this session use\" (narrow usage only) → `session-stats`\n- \"what tasks are pending across my sessions\" → `session-tasks`\n- \"what happened in the session where I fixed the login bug\" (session identified by content, not yet\n  located) → `session-search`\n\n**Quality gates:**\n- [ ] `\u003Csession-path>` in Step 3 is explicitly derived from Step 1's `session.path` field\n","# Session Detail\n\nShow comprehensive details about a single session.\n\n## When to Use\n\n- Wants the full picture of one session: summary, tasks, and message transcript\n- \"show session\", \"session details\", \"what happened in session X\"\n\n## When NOT to Use\n\n- A dedicated token-usage\u002Fcost\u002Fmodel breakdown only, not the full profile → use `session-stats` instead\n- Cross-session task aggregation → use `session-tasks` instead\n- The target session isn't yet identified — described by content\u002Ftopic rather than an ID or clear\n  reference (e.g. \"what happened in the session where I fixed the login bug\") → use `session-search`\n  first to locate it; use `session-detail` once a specific session is identified.\n- Wants a portable recovery document for a *different* session, not live detail here → use\n  `session-resume` instead.\n- Wants a comparison between two sessions, not detail on one → use `session-diff` instead.\n- Wants only a bare chronological, event-by-event timeline for one session (no summary or task\n  context) → use `session-timeline`'s single-session mode (its Step 1, Option B) instead.\n- Wants a file\u002Ftranscript export, not detail shown in the conversation → use `session-export` instead.\n\n## Step 1: Get session detail\n\nIf no session ID is given, resolve the live session directly (safe even when the current working\ndirectory doesn't match where the session actually started — e.g. a worktree created mid-session):\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_store.py\" current\n```\n\nOtherwise:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_store.py\" session-detail \u003Csession-id>\n```\n\nThis returns: session summary (including the `path` field), token usage (input\u002Foutput\u002Fcache), models used, tools called, and associated task lists with their tasks. This command always prints JSON — no `--format` flag needed.\n\n## Step 2: Present summary\n\nShow a formatted summary:\n\n- **Session**: ID, project, date, duration\n- **Tokens**: input, output, cache read, cache create\n- **Models**: which models were used and how many turns each\n- **Tools**: top tools used with counts\n- **Tasks**: associated task lists and task status summary\n\n## Note on resumed sessions\n\nIf `is_resumed` is true in the stats, this session was started via `claude --resume` or `claude --continue`. The JSONL only contains messages from the resumed portion — earlier context from the parent session is not included. Mention this to the user so they understand why the transcript may appear to start mid-conversation.\n\n## Step 3: Show messages (optional)\n\nIf the user wants to see the conversation, use the `path` field from Step 1's `session` object:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\" messages \u003Csession-path> --limit 20\n```\n\nFor more messages, increase `--offset` and `--limit`:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\" messages \u003Csession-path> --offset 20 --limit 20\n```\n\nTo include tool call details:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\" messages \u003Csession-path> --include-tools --limit 20\n```\n\n## Testing & Validation\n\nEval suite: `evals\u002Fsession-detail\u002F` — 3 scenarios, `skill-tester` Quick Workflow blind comparison, all\npassed. Eval 3 verified a cross-session task query correctly redirects to `session-tasks` instead of\nbeing answered directly.\n\n**Last dated run record:** `evals\u002Fsession-detail\u002Fworkspace\u002Fiteration-2\u002Feval-{1,2,3}\u002Fwith_skill\u002Fgrading.json`,\n2026-09-03. `scripts\u002Fsmoke_test.py` structural self-check also passing as of the same date.\n\n**Verify this skill activates on:**\n- \"show session details for X\"\n- \"what happened in session X\"\n- \"give me the full picture of this session\"\n\n**Verify it does NOT activate on:**\n- \"how many tokens did this session use\" (narrow usage only) → `session-stats`\n- \"what tasks are pending across my sessions\" → `session-tasks`\n- \"what happened in the session where I fixed the login bug\" (session identified by content, not yet\n  located) → `session-search`\n\n**Quality gates:**\n- [ ] `\u003Csession-path>` in Step 3 is explicitly derived from Step 1's `session.path` field\n",{"name":5,"description":7,"allowed-tools":23},"Bash(python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_store.py\":*) Bash(python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fsession_transcript.py\":*)","main","1bf12900cac6f28e346abd2912bdb78d306de723","plugins\u002Fsession-kit\u002Fskills\u002Fsession-detail","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace","https:\u002F\u002Fgithub.com\u002FAndreHahm","2026-11-15 04:26:16",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add AndreHahm\u002Fandres-cc-marketplace --skill session-detail",{"tool":36,"command":37},"bunx","bunx skills add AndreHahm\u002Fandres-cc-marketplace --skill session-detail",{"tool":39,"command":40},"pnpm","pnpm dlx skills add AndreHahm\u002Fandres-cc-marketplace --skill session-detail","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-kit\u002Fskills\u002Fsession-detail\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"scripts\u002Fsmoke_test.py","SCRIPT","脚本",7976,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-kit\u002Fskills\u002Fsession-detail\u002Fscripts\u002Fsmoke_test.py",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M79R0K918Z0XDM74R0EY5H3P","demo","Fixture skill used by scripts.marketplace_ci sync tests.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Ftests\u002Fmarketplace_ci\u002Ffixtures\u002Fplugins\u002Fsample-kit\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M79R08VMDJA2FPJKH3ZM309K","export-demo","Fixture skill used by scripts.marketplace_ci export tests.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Ftests\u002Fmarketplace_ci\u002Ffixtures\u002Fclaude\u002Fskills\u002Fexport-demo\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M79R042FS581DS2JNW5AZ1MK","work-to-development","Validate an accepted Linear Issue's readiness for implementation (criteria, dependencies, duplicate\u002Fexisting artifacts) and request governed branch\u002Fworktree creation through git-kit:starting-work — recording work-started Git\u002FGitHub evidence and a deliberate Linear Started transition only after Git identity is read back and verified. Use when asked to start work on a Linear issue, begin development for an accepted issue, or prepare an accepted issue for implementation. Never creates a branch directly — always delegates to git-kit.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Fwork-to-development\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79QZZD4EHB82P72P4N92BKT","work-linking","Create and maintain stable cross-system links and authority labels between Notion and Linear records, and detect\u002Frepair drift between them. Use when asked to link a Notion record to a Linear record, check for drift between Notion and Linear, or repair a broken\u002Fstale link. Repairs only the bounded non-authoritative copy or link — never chooses by newest timestamp, and never creates a reverse-write loop against either system's own authority.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Fwork-linking\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M79QZVFA3GTVNZMJ51NESVSP","status-and-learning","Produce a dated, explicitly non-live Linear-to-Notion progress summary, or capture an outcome\u002Flearning after work completes. Use when asked to summarize progress to Notion, report portfolio status, or capture what was learned from a completed piece of work — not to disposition open follow-up items (see open-item-management for that). Never runs automatically or continuously — every summary is a deliberate, approved snapshot, not a live sync.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Fstatus-and-learning\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M79QZNSKSABK7X2PT93X8QT5","repository-gates","Discover, delegate, record, and invalidate this repository's actual Git\u002FGitHub lifecycle gates (pre-commit, pre-push, PR required checks, Codex delta review, review requirements, merge rights) and the repository-policy provider profile that maps governed operations to git-kit. Use when asked what gates apply to this repository, to discover repository policy before starting Wave 2 work, or to check whether prior gate evidence is still valid after new commits. Discovery and delegation only — never executes a gate's own internal logic, and never invents a gate the repository doesn't actually define (in particular, never assumes a \"Review Changes\" gate exists).","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Frepository-gates\u002FSKILL.md",[],[]]