Agent skill · writing content · delphine-l
claude-collaboration
Best practices for using Claude Code in team environments. Covers skill management, knowledge capture, version control, and collaborative workflows.
Why this skill is useful
Provides specific guidelines for managing Claude Code skills in team environments, which the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-05-14. 17 stars on the source repository.
What this skill does
Claude Code Collaboration Best Practices This skill provides guidance on effectively using Claude Code in team environments, managing shared knowledge through skills, and maximizing value from AI-assisted development. Core Principles 1. Skills are living documentation - They evolve as you learn 2. Capture knowledge explicitly - Claude doesn't auto-update skills 3. All skills live in $CLAUDEMETADATA - No local skills or commands in projects 4. Share knowledge across the team - Centralized repo ensures consistency 5. Version control your skills - Track changes and improvements 6. Be intentional about updates - Not everything learned needs to be captured Critical: No Local Skills or Commands ALL skills and commands MUST be in the $CLAUDEMETADATA repository, never in individual project directories. Never do this: Always do this: Why centralization is mandatory: Version control: All skills tracked in one git repo Team sharing: Everyone uses the same knowledge Consistency: No divergence between projects Maintenance: Update once, applies everywhere Discovery: Team can see all available skills Even project-specific skills go in the central repo under $CLAUDEMETADATA/skills/project-name/. --- Understanding How Skills Work What Happens During a Session At session start: Claude reads all .claude/skills/ files in your directory Skills provide context and guidelines for the session Knowledge from skills is "loaded" into Claude's working context During the session: Claude learns from your conversation (temporary, in-context learning) Solutions discovered apply only to this conversation Skills remain unchanged unless you explicitly update them At session end: All temporary learning is lost Skills remain exactly as they were at the start Next session starts fresh, reading skills again What This Means Skills persist across sessions - They're files on disk Session learnings don't persist - They exist only in conversation context You must explicitly update skills - Claude won't do it …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills delphine-l/collaboration