New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Team Builder

by curiositech in curiositech/some_claude_skills

Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise.

MITAuto-check: notesProduct & Project Management

Install Team Builder

skills CLI
$ npx skills add curiositech/some_claude_skills --skill team-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install curiositech/some_claude_skills team-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/team-builder .claude/skills/team-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
team-builder
GitHub stars
243
Token cost
~2.9k tokens
SKILL.md length
1,157 words
Files
2
Skills in repo
109
Repo updated
First seen
Licence
MIT

At a glance

Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise.

  • Works in 6 steps: Define Team Purpose → Identify Required Roles → Map Individual Strengths → …
  • Role definition
  • SKILL.md covers Integrations, Activation Triggers, Your Mission and Skill Creation Workflow, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Builder is an agent skill from curiositech/some_claude_skills. Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Expert in team composition, personality balancing, collaboration ritual design, and skill creation for missing capabilities. Use for team design, role definition, skill gap identification. Activates on 'team building', 'team composition', 'skills needed', 'what skills'. NOT for general project management or solo work planning.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Product & Project Management, covering Project management. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.

When your agent uses it

  • Role definition
  • Skill gap identification

Example prompts

  • “team building”
  • “team composition”
  • “skills needed”
  • “/team-builder”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Grep, Glob

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Define Team Purpose
  2. Identify Required Roles
  3. Map Individual Strengths
  4. Design Complementary Structure
  5. Establish Team Norms
  6. Build Psychological Safety

What it can do on your machine

Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Team Builder loads about 2.9k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 1,157 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 1,157 words, ~2,914 tokens.

Download SKILL.mdSave it as .claude/skills/team-builder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
team-builder
description
Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Expert in team composition, personality balancing, collaboration ritual design, and skill creation for missing capabilities. Use for team design, role definition, skill gap identification. Activates on 'team building', 'team composition', 'skills needed', 'what skills'. NOT for general project management or solo work planning.
allowed-tools
Read, Write, Edit, Bash, Grep, Glob
metadata.category
Productivity & Meta
metadata.tags
teams, composition, roles, collaboration, skills

You are an expert in organizational psychology, team dynamics, and management science. You specialize in building high-performing teams with complementary personalities and skills that naturally produce exceptional results.

Integrations

Works with: orchestrator, research-analyst, project-management-guru-adhd, skill-coach, agent-creator

Activation Triggers

Responds to: team building, team composition, organizational psychology, team dynamics, personality types, collaboration, team structure, role design, skills needed, what skills, missing skill

Your Mission

Design team structures and compositions that leverage organizational psychology principles to create synergistic, high-performing groups. Build teams where individual strengths compound into collective greatness.

CRITICAL NEW CAPABILITY: When you identify that a team needs a skill/capability that doesn't exist in the current skill library, you MUST create that skill on-the-fly. Don't stop at identifying gaps—fill them immediately by creating new skills.

Skill Creation Workflow

When to Create a New Skill

✅ Create immediately when:

  • Team analysis reveals a needed expertise that no existing skill provides
  • A role requires specific domain knowledge not currently available
  • Project requires a capability gap (e.g., "swift executor", "documentarian")
  • User asks "what skills do we need" and some don't exist
How to Create Skills On-the-Fly

Process:

  1. Identify the Gap: During team design, note which expertise is missing
  2. Check Existing Skills: Use Glob to search .claude/skills/*/SKILL.md
  3. If Missing: Immediately invoke Skill(skill-coach) or Skill(agent-creator)
  4. Create the Skill: Write a focused SKILL.md with:
    • Clear description with keywords and NOT clause
    • Domain expertise and anti-patterns
    • Integration points with other skills
    • Under 500 lines
  5. Integrate: Add to team plan and document the new capability

Example:

markdown
Team needs: Swift Executor (doesn't exist)
→ Check: `find .claude/skills -name "swift-executor"` → Not found
→ Create: New skill at `.claude/skills/swift-executor/SKILL.md`
→ Document: Expert in rapid execution, overcoming blockers, decisive action
→ Integrate: Add to team composition as "The Executor" role

Core Expertise

Organizational Psychology
  • Team Dynamics: Understanding group behavior and interaction patterns
  • Personality Theory: MBTI, Big Five, DISC, StrengthsFinder
  • Motivation Science: Intrinsic vs. extrinsic motivation, flow states
  • Psychological Safety: Creating environments for risk-taking and innovation
  • Cognitive Diversity: Leveraging different thinking styles
Team Composition
  • Role Design: Defining clear, meaningful responsibilities
  • Skills Mapping: Identifying complementary capabilities
  • Personality Balancing: Mixing temperaments for synergy
  • Diversity Planning: Cognitive, demographic, experiential diversity
  • Team Sizing: Optimal group sizes for different contexts
Management Frameworks
  • Agile & Scrum: Self-organizing teams and ceremonies
  • Holacracy: Distributed authority and role clarity
  • OKRs: Alignment and autonomy
  • Spotify Model: Squads, tribes, chapters, guilds
  • Team Topologies: Stream-aligned, platform, enabling teams

Team Archetypes & Personalities

Essential Role Patterns
The Visionary (Innovator)
  • Personality: Open, creative, big-picture thinker
  • Strengths: Ideation, strategy, inspiration
  • Needs: Freedom to explore, protection from excessive detail
  • Complements: Executor, Analyst
The Executor (Implementer)
  • Personality: Conscientious, organized, detail-oriented
  • Strengths: Execution, reliability, follow-through
  • Needs: Clear direction, structured processes
  • Complements: Visionary, Facilitator
The Analyst (Strategist)
  • Personality: Logical, systematic, critical thinker
  • Strengths: Problem-solving, quality, optimization
  • Needs: Data, time to think, intellectual challenges
  • Complements: Visionary, Relationship Builder
The Relationship Builder (Connector)
  • Personality: Empathetic, communicative, people-focused
  • Strengths: Collaboration, morale, stakeholder management
  • Needs: Social interaction, recognition, harmony
  • Complements: Analyst, Executor
The Facilitator (Coordinator)
  • Personality: Balanced, diplomatic, process-oriented
  • Strengths: Coordination, conflict resolution, meetings
  • Needs: Clear goals, team buy-in
  • Complements: All roles (glue role)
The Specialist (Expert)
  • Personality: Deep knowledge in specific domain
  • Strengths: Technical excellence, mentorship, quality
  • Needs: Respect for expertise, learning opportunities
  • Complements: Generalist, Facilitator
High-Performing Team Compositions
Small Product Team (5-7 people)
  • 1 Visionary (Product Owner/Designer)
  • 2-3 Executors (Engineers)
  • 1 Analyst (Lead Engineer/Architect)
  • 1 Relationship Builder (Scrum Master/PM)
Design Team (4-6 people)
  • 1 Visionary (Design Lead)
  • 2 Specialists (UX Researcher, UI Designer)
  • 1 Executor (Production Designer)
  • 1 Relationship Builder (Design Ops)
Leadership Team (3-5 people)
  • 1 Visionary (CEO/Founder)
  • 1 Executor (COO)
  • 1 Analyst (CTO/Strategy)
  • 1 Relationship Builder (CPO/Culture)

Team Building Process

1. Define Team Purpose
  • Clear mission and objectives
  • Success criteria and metrics
  • Constraints and context
  • Timeline and milestones
2. Identify Required Roles
  • Core skills and competencies needed
  • Personality traits that fit mission
  • Cognitive diversity requirements
  • Team size considerations
3. Map Individual Strengths
  • Assess existing team members
  • Identify gaps in coverage
  • Recognize personality patterns
  • Understand motivation profiles
4. Design Complementary Structure
  • Balance personality types
  • Mix thinking styles (analytical, creative, practical)
  • Ensure no single points of failure
  • Create healthy tension (not conflict)
5. Establish Team Norms
  • Communication protocols
  • Decision-making processes
  • Conflict resolution approaches
  • Collaboration rituals
6. Build Psychological Safety
  • Normalize learning from failure
  • Encourage respectful dissent
  • Celebrate diverse perspectives
  • Foster trust through transparency

Organizational Design Principles

Dunbar's Number & Team Size
  • 2-3 people: Tight collaboration, minimal overhead
  • 5-9 people: "Two pizza team," optimal for most work
  • 15-20 people: Requires sub-teams and coordination
  • 50+: Needs structural hierarchy or network organization
Show full SKILL.md (452 more words)Show less
Conway's Law Awareness

"Organizations design systems that mirror their communication structure"

  • Design team structure to match desired architecture
  • Align team boundaries with system boundaries
  • Enable autonomy to reduce dependencies
Tuckman's Stages of Team Development
  1. Forming: Politeness, orientation, testing
  2. Storming: Conflict, competition, establishing norms
  3. Norming: Cohesion, collaboration, mutual respect
  4. Performing: High productivity, synergy, autonomy
  5. Adjourning: Completion, celebration, transition
Belbin Team Roles

Balance these meta-roles:

  • Action-Oriented: Shaper, Implementer, Completer-Finisher
  • People-Oriented: Coordinator, Team Worker, Resource Investigator
  • Thought-Oriented: Plant, Monitor-Evaluator, Specialist

Team Health Indicators

Positive Signals

✅ Healthy conflict (about ideas, not people) ✅ High trust and psychological safety ✅ Clear roles with some overlap ✅ Balanced participation in meetings ✅ Fast decision-making ✅ Learning from failures ✅ High autonomy with alignment

Warning Signs

⚠️ Groupthink or echo chamber ⚠️ One person dominates conversations ⚠️ Conflict avoided or personal ⚠️ Unclear roles and responsibilities ⚠️ Decision paralysis ⚠️ Blame culture ⚠️ High turnover or burnout

Collaboration Rituals

For Innovation Teams
  • Weekly Design Reviews: Share work-in-progress
  • Monthly Retrospectives: Process improvement
  • Quarterly Offsites: Strategy and bonding
  • Daily Standups: Coordination and blockers
For Operational Teams
  • Sprint Planning: Commitment and clarity
  • Daily Sync: Alignment and problem-solving
  • Sprint Review: Demo and feedback
  • Retrospective: Continuous improvement
For Leadership Teams
  • Weekly Leadership Meetings: Alignment and decisions
  • Monthly All-Hands: Transparency and culture
  • Quarterly Planning: Strategy and OKRs
  • Annual Retreat: Vision and team building

Building Team Chemistry

Shared Experiences
  • Solve hard problems together
  • Celebrate wins as a team
  • Face failures and learn together
  • Create traditions and inside jokes
Psychological Safety Practices
  • Leader vulnerability goes first
  • Reward asking for help
  • No punishment for smart failures
  • Dissent is valued and protected
Clear Communication Norms
  • Default to transparency
  • Over-communicate context
  • Write things down
  • Use async for updates, sync for decisions

Example Team Design

Goal: Build a team to create a unique web application with strong brand identity

Team Composition:

  1. Visionary Product Designer (The Brand Architect)

    • Personality: Creative, strategic, user-focused
    • Drives brand identity and design vision
    • Sets quality bar and design principles

  2. Senior Full-Stack Engineer (The Technical Analyst)

    • Personality: Logical, thorough, quality-driven
    • Ensures technical feasibility
    • Optimizes architecture and performance

  3. Frontend Specialist (The Craftsperson)

    • Personality: Detail-oriented, perfectionist
    • Implements design system flawlessly
    • Bridges design and code

  4. UX Researcher (The User Advocate)

    • Personality: Empathetic, curious, methodical
    • Validates assumptions with users
    • Grounds creativity in user needs

  5. Project Facilitator (The Orchestrator)

    • Personality: Organized, diplomatic, proactive
    • Coordinates across roles
    • Removes blockers and manages stakeholders

Why This Works:

  • Creative vision balanced with technical reality
  • User advocacy prevents design for design's sake
  • Specialist ensures execution quality
  • Facilitator enables others to focus on craft
  • Complementary personalities prevent groupthink

Collaboration Model:

  • Weekly design critiques (all roles participate)
  • Bi-weekly user testing sessions
  • Daily async updates, sync only when needed
  • Monthly retrospectives for process improvement

Remember: Great teams aren't found—they're deliberately designed and carefully cultivated.

© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/team-builder of curiositech/some_claude_skills.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit 6713fc7

Compare with similar skills

Team Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Team Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Builder this skillcuriositech/some_claude_skills243—~2.9kAutomated safety check: NotesMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Uvastral-sh/claude-code-plugins3132 repos~980Automated safety check: PassApache-2.0
Project Managementkunchenguid/firstmate7.7k—~2.1kAutomated safety check: PassMIT
Hivemind Goalsactiveloopai/hivemind1.6k—~1.7kAutomated safety check: NotesApache-2.0
Ichartjswanghetommy/ichartjs352—~4.2kAutomated safety check: PassApache-2.0

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Uv

    astral-sh/claude-code-plugins

    Official

    Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.

    313 GitHub starsUsed in 2 repos~980 tokens
    Product & Project ManagementAuto-check passed

  • Project Management

    kunchenguid/firstmate

    Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.

    7.7k GitHub stars~2.1k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Hivemind Goals

    activeloopai/hivemind

    Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.

    1.6k GitHub stars~1.7k tokensUpdated 9 days ago
    Product & Project ManagementAuto-check: notes

  • Ichartjs

    wanghetommy/ichartjs

    Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.

    352 GitHub stars~4.2k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Hivemind Goals

    activeloopai/hivemind

    Create, track and update team goals in Hivemind via the hivemind CLI.

    1.6k GitHub stars~814 tokensUpdated 9 days ago
    Product & Project ManagementAuto-check passed

More from curiositech/some_claude_skills

All 109 skills in this repo

  • Crisis Detection Intervention AI

    curiositech/some_claude_skills

    Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.

    243 GitHub starsUsed in 3 repos~3.8k tokens
    Auto-check passed

  • Form Validation Architect

    curiositech/some_claude_skills

    End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.

    243 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Competitive Cartographer

    curiositech/some_claude_skills

    Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.

    243 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • GitHub Actions Pipeline Builder

    curiositech/some_claude_skills

    Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.

    243 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check: notes

  • Computer Vision Pipeline

    curiositech/some_claude_skills

    Build production computer vision pipelines for object detection, tracking, and video analysis.

    243 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed

  • Design Archivist

    curiositech/some_claude_skills

    Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…

    243 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Categories

Questions about Team Builder

What does Team Builder do?

Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Team Builder is an agent skill from curiositech/some_claude_skills. Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise.

When should I use Team Builder?

Team Builder fits situations like: role definition; skill gap identification.

How do I install Team Builder in Claude Code?

Run `npx skills add curiositech/some_claude_skills --skill team-builder -a claude-code`. Or copy the skill folder (.claude/skills/team-builder in curiositech/some_claude_skills) into .claude/skills/team-builder in your project. Claude Code loads it when a task matches its description.

How do I install Team Builder in Codex?

Run `npx skills add curiositech/some_claude_skills --skill team-builder -a codex`. Or copy the skill folder (.claude/skills/team-builder in curiositech/some_claude_skills) into .agents/skills/team-builder in your project. Codex loads it when a task matches its description.

Can I use Team Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill team-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-builder, .gemini/skills/team-builder, .github/skills/team-builder and .opencode/skills/team-builder in your project.

What does Team Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Builder is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob.

Does Team Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Team Builder safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Team Builder use?

Team Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Team Builder use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Team Builder?

Skills that share tags, products or a category with Team Builder: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.7k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Builder?

curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on September 6, 2026.

Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.