finished
From the author
End-of-session closure for a research or code repository. Records what changed into the project's own handoff and log files, separating verified work from work merely attempted, and reports what is left uncommitted. Use when wrapping up a session so the next one can resume without re-deriving state. Its start-of-session twin is sitrep.
Install
npx skills add scdenney/open-science-skills --skill finished -a claude-code
Installs to .claude/skills/finished/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- sitrepscdenney/open-science-skillsStart-of-session situational report for a research or code repository. Reads the handoff, log, or status files the project actually keeps, checks live git state, and reports the objective, verified baseline, open tasks, blockers, and next actions, flagging where the documents and the repository disagree. Use when resuming work after time away or before changing anything. Its end-of-session twin is finished.Science★ 69
- wrap-upPaulRBerg/agent-skillsWind down a long-running session fast when the user must leave — freeze new work, preserve active subagents, secure finished work, and hand off the remainder via task-handoff.Productivity★ 101
- os-done-or-notkharmanskyi/open-stepsALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from you, new debt, safe to close. Every "yes" names its proof; unverified says "not checked". Saves the report so the next session starts from it instead of re-exploring the repo.Other★ 1.2K
- session-handoffOneWave-AI/claude-skillsUse when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume without re-reading the transcript.Writing★ 378
- issuespedrohcgs/claude-code-my-workflowKeeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as its own issue without duplicates, lists the open issues that bear on the current work, and closes an issue with a comment recording what was wrong, what was tried, what worked, and how it was fixed. Use when review findings or a list of problems should become tracked work (a paper's misleading claims, a codebase's bugs, improvements for later), when starting or resuming work and deciding what to do next, or when a fix has landed and its issue should be closed with a record. Needs the GitHub CLI; warns before posting to a public repository.Science★ 1.7K
- handoffOyadotAI/oya-browserSummarize the current work so another session can continue it.Productivity★ 351
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in