PA

paper-connections-session-summary

Summarizes session outcomes and updates durable project documentation.

Install

mkdir -p .claude/skills/paper-connections-session-summary && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13045" && unzip -o skill.zip -d .claude/skills/paper-connections-session-summary && rm skill.zip

Installs to .claude/skills/paper-connections-session-summary

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Update durable workflow/docs and write a new Paper Connections session summary for the current worktree. Use near session close-out when the user asks to summarize lessons learned, create a new session summary, or says `总结沉淀`.
226 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Re-read AGENTS.md before editing docs.
  • Identify the current branch/worktree.
  • Inspect current-session scope with small git checks.
  • Update AGENTS.md for reusable workflow rules.
  • Create a new session summary file.
  • Keep the summary compact and practical.

How it works

The skill re-reads AGENTS.md, identifies the current worktree, inspects the session scope, and updates durable documentation only when repeatable knowledge is produced.

Inputs & outputs

You give it
User asks to summarize lessons learned or create a new session summary.
You get back
A new session summary file for the current worktree and updated durable docs.

When to use paper-connections-session-summary

  • Close session summary
  • Update workflow rules
  • Document session decisions

About this skill

Paper Connections Session Summary

Close out a Paper Connections work session by updating durable docs only where needed and creating a fresh session summary for the current worktree.

Workflow

  1. Re-read AGENTS.md before editing docs.
  2. Identify the current branch/worktree so the summary filename matches the current workspace.
  3. Inspect current-session scope with small git checks such as git status --short and git log --oneline --decorate -n 20.
  4. Update durable docs only when the session produced repeatable knowledge:
    • AGENTS.md for reusable workflow rules, skill triggers, or repeatable engineering lessons.
    • doc/current-features.md if user-visible behavior changed in this session and the file is not already current.
    • doc/storage-crud.md if data model or CRUD/API behavior changed.
  5. Create a new session summary file by following references/session-summary-checklist.md.
  6. Keep the summary compact and practical:
    • what changed in this session
    • important refinements/decisions
    • doc/workflow updates
    • validation/build results
    • key commits already created during the session, if any
  7. If the session changed files under src/, open .codex/skills/paper-connections-build-check/SKILL.md and run that verification flow before close-out.

Scope

  • Prefer concise summaries over full chronological logs.
  • Do not rewrite older session summaries; add a new one for the current session.
  • Avoid touching docs that were unaffected by the session just to make them look uniform.

When not to use it

  • When full chronological logs are preferred over concise summaries.
  • When older session summaries need rewriting.
  • When docs unaffected by the session need uniform styling.

Limitations

  • It does not rewrite older session summaries.
  • It avoids touching unaffected documents for uniformity.
  • It prefers concise summaries over full chronological logs.

How it compares

This skill automates the process of updating specific documentation and creating a session summary based on defined criteria, unlike manually sifting through changes and deciding what to document.

Compared to similar skills

paper-connections-session-summary side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
paper-connections-session-summary (this skill)05moNo flagsBeginner
notion-knowledge-capture109moNo flagsIntermediate
history-insight07moReviewBeginner
log06moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

notion-knowledge-capture

makenotion

Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.

10115

history-insight

team-attention

This skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").

02

log

dev-whitecrow

기록 스킬. 중요한 의사결정이나 순간을 Decision_Log나 History에 빠르게 기록합니다.

00

distill

dev-whitecrow

정제 스킬. Inbox의 날것의 생각(Raw Data)을 읽어 분석하고, 이를 The_Ark의 적절한 위치에 구조화하여 배치합니다. 온보딩 단계에 따라 다르게 작동합니다.

00

wiki-fileback

GYF0311

把对话中产生的洞察/决策/事实按主语写回 corpus,追加 timeline 或新建页面。触发词:记一下、存下来、笔记、把刚才那个放进去、fileback、存回知识库。

00

kb-audit

roman-karpovich

Audit / curate KB-vault hygiene — surfaces mechanical drift (broken [[wikilinks]], dangling §-pointers, status-enum violations, status-drift, index-row bloat) the librarian's KB-curator role consumes. REPORTS only; never auto-edits the vault. Use to check KB drift, audit the KB, or do KB hygiene.

00

Search skills

Search the agent skills registry