Collab Proof
Use when you want to understand what Claude contributed vs what you drove in a session.
Before & after
Same prompt, same agent — the only difference is the skill.
That's an interesting question. I can try to look back at what happened in our conversation and break it down. Typically, I might have helped with brainstorming, offering suggestions, or refining ideas you already had. You probably came up with the core concept and direction. I might have filled in details or asked clarifying questions. It's hard to say exactly without looking at the specific conversation, but usually it's a mix of your ideas being shaped by my input and suggestions. Different people value collaboration differently, so what counts as a contribution might vary.
COLLABORATION BREAKDOWN YOU DROVE (core direction) → Chose design system color palette (brand primary + accent) → Decided on 5-column grid vs 6-column (you tested both mockups) → Selected navigation pattern (top bar vs sidebar) → Reviewed competitive set and rejected 3 approaches → Final sign-off on design: 100% your decision CLAUDE CONTRIBUTED (refinement + iteration) → Generated 8 design variations given your constraints (30 min) → Named components following your naming convention → Audited accessibility (contrast, spacing, touch targets) → flagged 2 issues, you fixed → Suggested typography pairing (you approved without change) → Wrote CSS-in-JS template (you adapted to your framework) → Documented 12 component specs → you used 11, modified 1 TO-TALS Decisions: 12 | You made: 8 (67%) | Claude made: 4 (33%) File outputs: 8 | You authored: 2 | Claude generated: 6 Time saved (estimated): 2.5 hours of iteration + documentation BOTTOM LINE → You controlled direction, vision, final approvals → Claude handled speed (faster variation) and polish (specs, a11y) → High collaboration ratio (33% Claude input is typical for design-led projects) FILE: collab-proof.json logged in project memory
About this skill
name: collab-proof description: Use when Use when you want to understand what Claude contributed vs what you drove in a session.
Collab Proof
Use when you want to understand what Claude contributed vs what you drove in a session. Triggers on: /collab-proof, session retrospective, ai contribution analysis, collaboration evidence, what did claude do.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the collab-proof skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Collab Proof; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: collab-proof
description: Use this skill when reviewing a session to understand what Claude actually contributed versus what the user drove themselves.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Collab Proof
Produces a clear breakdown of what an agent contributed in a session versus what the user directed, for retrospective or collaboration-evidence purposes.
## When to use
- Running a session retrospective to understand the actual division of work
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.