conversation-dump

Included with Lifetime

$97 forever

This skill should be used when the user asks to "dump this conversation", "save this conversation to markdown", "output this conversation to a markdown file", "export this chat", "log this session to a file", "save this chat log", or similar. Produces a structured, readable capture of the current Pi conversation - user requests verbatim, assistant responses in full, commands plus key output inline, decisions preserved - not a brief summary. Distinct from mischief-managed, which writes a compact Obsidian session note.

Writing & Docs

What this skill does

# Conversation Dump - Full Markdown Transcript

Create a faithful Markdown record of the current Pi conversation. This is for full-fidelity capture, not an end-of-session summary.

## Use When

Use this skill when the user asks to:

- dump this conversation
- save this conversation to Markdown
- export this chat
- log this session to a file
- save the chat log
- output the full transcript

Do **not** trigger on Mischief Managed territory, such as "wrap up this session," "save a session summary," or "write this to Pi-Sessions." Mischief Managed writes a compact summary. Conversation Dump writes the full readable transcript.

## Output Goal

The Markdown file should preserve:

- user requests as close to verbatim as possible
- assistant responses in full when available in context
- tool calls and commands that materially changed state
- key command output, summarized only when output is huge
- file paths touched
- decisions made
- follow-up items

Do not reduce the session to a short summary. Prefer a structured transcript with enough context that future-you can reconstruct what happened.

## Destination

Use this priority order:

1. explicit path or folder requested by the user
2. current working directory if the user says "here" or implies the repo/project
3. ask one clarifying question if destination is unclear

Good default filename:

```text
conversation-dump-{YYYY-MM-DD-HHMM}-{short-slug}.md
```

If the user wants it in Obsidian, use the user-provided vault path. Do not assume the Pi session summary folder unless they explicitly ask for it.

## Workflow

### 1. Gather metadata

Run one shell command:

```bash
date +%Y-%m-%d-%H%M; date +"%b %d, %Y"; pwd; git rev-parse --abbrev-ref HEAD 2>/dev/null || echo ""; basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo ""; git remote get-url origin 2>/dev/null || echo ""
```

Map to:

- `DATETIME`
- `PRETTY_DATE`
- `DIR`
- `BRANCH`
- `REPO`
- `REPO_URL`

### 2. Build the dump

Use this structure:

```markdown
---
date: {DATETIME}
type: conversation-dump
directory: {DIR}
branch: {BRANCH} # omit if empty
repo: {REPO} # omit if empty
repo_url: {REPO_URL} # omit if empty
---

# Conversation Dump: {SHORT TITLE} - {PRETTY_DATE}

## Context
- Working directory: `{DIR}`
- Goal: ...

## Timeline

### 1. User
> Verbatim user request.

### 2. Assistant
Assistant response in full, or a faithful reconstruction if exact text is not available.

### 3. Tool / Command
```bash
command here
```

Key output:
```text
important output here
```

## Files Changed
- `path` - what changed

## Decisions Preserved
- decision - rationale

## Follow-ups
- [ ] item
```

Number turns sequentially. Keep command output readable: include exact short output; for huge output, include the relevant excerpt and note that output was truncated.

### 3. Write the file

Use one write operation when possible. Let the write tool create missing parent directories.

### 4. Confirm

Return:

- full path written
- one sentence describing what was captured
- any caveat about omitted or truncated output

Files: 1

Size: 3.6 KB

Complexity: 16/100

Category: Writing & Docs

Source: https://github.com/ethanolivertroy/public-skills/tree/main/skills/conversation-dump

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts