agentleFS
michele-orsini-71michele-orsini-71/claude-skills/project-wrap-up/SKILL.md

project-wrap-up

Skill0 starsChanged 6 months agoMITView on GitHub

Save all Claude conversations for the current project, distill them into a comprehensive report, and clean up. Use when closing or wrapping up a project.

  • Deletes or force-pushes

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the save script to extract all conversations as markdown:

    line 26
  2. Distinctive:

    If the script fails (e.g., no conversations found, jq missing), report the error to the user and stop.

    line 32
  3. Distinctive:

    Read the distiller agent definition:

    line 36
  4. Distinctive:

    Wait for the subagent to complete.

    line 49
  5. Distinctive:

    Remove the temporary folder:

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Wrap-Up

You orchestrate a project wrap-up workflow. Follow these steps in order.

Step 1: Compute the output filename

Determine the project folder name and build the report filename:

basename "$(pwd)"

The report will be named <folder-name>-project-wrapup.md in the project root.

Step 2: Save conversations

Run the save script to extract all conversations as markdown:

bash "${CLAUDE_SKILL_DIR}/scripts/save-all-conversations.sh" "$(pwd)" ".wrap-up-temp"

If the script fails (e.g., no conversations found, jq missing), report the error to the user and stop.

Step 3: Distill conversations

Read the distiller agent definition:

cat "${CLAUDE_SKILL_DIR}/agents/conversation-distiller.md"

Launch a subagent using the Agent tool with:

  • prompt: The content of conversation-distiller.md (everything after the frontmatter --- block), followed by these specifics:
    • Input folder: .wrap-up-temp/
    • Output file: <folder-name>-project-wrapup.md (the name computed in step 1, in the project root)
  • model: sonnet

Wait for the subagent to complete. If it reports an error, relay it to the user.

Step 4: Clean up

Remove the temporary folder:

rm -rf .wrap-up-temp

Step 5: Report to the user

Tell the user:

  • The report filename and location
  • How many conversations were processed (from the save script output)
  • A brief (2-3 sentence) teaser of what the report covers

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.