OpenParable
Skip to content
← Back to skills

End

Productivity
end

End is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Finalize session by creating detailed log and syncing to cloud

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/productivity/end-3x-projetos-claude-memory-framew-2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/end, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

End Session

Quick Finalization Workflow

  1. Check for reflection (optional):

    • Check if .metrics-reflection.tmp exists
    • If NOT exists, ask: "Quick reflection before finishing? (y/n)"
    • If yes: Direct user to run /reflect first, then /end again
    • If no or file exists: Continue to step 2
  2. Collect session info: Prompt user for session summary (topic, projects touched, key activities, decisions, blockers)

  3. Capture performance metrics: Get actual values automatically:

    • Run: python3 ~/.claude/get-context-metrics.py to get: tokens|raw%|ctx(u)%|overhead
    • Parse output: 95641|47.8|59.8|12.0 means:
      • Context: 95,641 tokens
      • Tokens %: 47.8%
      • Context Window %: 59.8%
      • Overhead: 12.0 percentage points
  4. Merge reflection metrics (if .metrics-reflection.tmp exists):

    • Read and parse reflection file
    • Merge with automatic metrics for log entry
    • Delete .metrics-reflection.tmp after merge
  5. Generate daily log entry: Create structured log in ~/.claude-memory/providers/claude/logs/daily/YYYY.MM.DD.md with:

    • Session timestamp + topic
    • Projects touched
    • Activities realized
    • Performance metrics (automatic + reflection if available)
    • Next steps
    • Decisions/insights
  6. Update session state: Modify ~/.claude-memory/providers/claude/session-state.md with current focus and pending tasks

  7. Update integration timeline: Append to ~/.claude-memory/integration/provider-activities.md and .quick.md

  8. Sync to cloud: Try pushing logs to cloud. On error, logs stay local only. (Cloud path in ~/.claude-memory/.config.json - don't read, just try sync)

  9. Confirmation: Show user what was logged and sync status

Performance Metrics Format

**Context Window**: [ctx(u)]% (real usage including Anthropic overhead)
**Tokens**: [used]/200,000 ([raw]%)
**Overhead**: [difference] percentage points

Example:

**Context Window**: 59.8% (real usage)
**Tokens**: 95,641/200,000 (47.8%)
**Overhead**: 12.0 percentage points

Why both matter:

  • Context Window % = What matters for hitting limits (includes system overhead)
  • Tokens % = Conversation size (useful for comparing sessions)
  • Overhead = Anthropic's cost (tools, prompts, cache, etc.)

Reflection Metrics Format (if available)

When .metrics-reflection.tmp exists, add this section to the log:

**Reflection** (self-reported):
- Satisfaction: X/10
- Energy: [Energizado/Neutro/Drenado]
- Frustration: [text or "None"]
- Notes: [text or empty]

Key Principle

Logs saved locally first, cloud sync is best-effort. Session finalization never blocks on cloud errors.


See existing daily logs for format examples.