mischief-managed

Included with Lifetime

$97 forever

Use when finishing a Pi, Codex, or other coding-agent session and wanting to save a lean Markdown session note into an Obsidian vault with decisions, code changes, validation, caveats, and follow-ups.

AI Agents

What this skill does


# Mischief Managed - Session Summary to Obsidian

Write a compact session note into an Obsidian vault so the work is searchable and resumable later. This is a summary, not a full transcript. For transcript-style capture in Pi, use the built-in `/export` command or `pi --export`.

## Obsidian Vault Location

Use this priority order:

1. If the user gives a vault path or note path, use it.
2. If `OBSIDIAN_VAULT_PATH` is set, write to `$OBSIDIAN_VAULT_PATH/Agent-Sessions/`.
3. If `~/Obsidian` exists, write to `~/Obsidian/Agent-Sessions/`.
4. Otherwise ask once for the Obsidian vault path before writing.

Do not silently write outside an Obsidian vault unless the user explicitly asks.

Filename:

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

Use a 2-4 word kebab-case slug based on the completed work.

## Metadata

Run one shell command to collect context:

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

Map output to:

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

If the git values are blank, omit them from frontmatter.

## Note Shape

```markdown
---
date: {DATETIME}
branch: {BRANCH}
repo: {REPO}
directory: {DIR}
tags: [agent-session, codex-session, {tag1}, {tag2}]
---

# Session: {SLUG} - {PRETTY_DATE}

## Summary
2-3 sentences describing what changed and why.

## What Was Discussed
- Short bullets with useful context.

## Key Decisions
- decision - rationale

## Code Changes
- `path` - what changed and why

## Tests & Validation
- `command` - result

## Risks / Caveats
- Anything unresolved, unverified, or worth revisiting.

## Questions & Follow-ups
- [ ] Concrete next action
```

Required sections: `Summary`, `What Was Discussed`, `Key Decisions`, and `Questions & Follow-ups`.

Include `Code Changes`, `Tests & Validation`, and `Risks / Caveats` only when meaningful.

## Content Rules

- Keep it lean. Capture durable facts, not every exchange.
- Preserve exact commands, filenames, issue IDs, URLs, and error messages when they matter.
- Prefer Obsidian-friendly Markdown: wikilinks are fine when the target note is obvious, but do not invent a vault taxonomy.
- Do not include secrets, tokens, cookies, API keys, or private credential material. Redact as `{REDACTED}` if needed.
- Do not post to external trackers or services unless the user explicitly asks in the current session.

## Confirmation

After writing, respond with:

- absolute note path
- one-line summary of what was captured

Files: 1

Size: 2.8 KB

Complexity: 7/100

Category: AI Agents

Source: https://github.com/ethanolivertroy/public-skills/tree/main/skills/mischief-managed

Related in AI Agents

skill-development

Included

Comprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.

AI Agentsscripts

reprompter

Included

Transform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.

AI Agentsscripts

adaptive-compaction

Included

Adaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.

AI Agentsscripts

agent-skill-creator

Included

Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.

AI Agentsscripts

llm-wiki

Included

Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.

AI Agentsscripts

skill-master

Included

Agent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.

AI Agentsscripts