team-collab-protocol

Encode a governance protocol for obsidian-docs-based team collaboration and handoffs.

3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/dadwadw233/team-collab-skills --skill team-collab-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-collab-protocol
Source: https://github.com/dadwadw233/team-collab-skills/tree/main/skills/protocol
Command: npx skills add https://github.com/dadwadw233/team-collab-skills --skill team-collab-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill encodes a governance protocol to guide AI-assisted team collaboration, standardizing project memory, handoffs, and cross-repo workflows.

Core Features & Use Cases

  • Establishes a structured, frontmatter-driven skill unit with activation signals, state quartet (CURRENT/NEXT/RISKS/TODO), and standardized handoff logs.
  • Enables consistent agent behavior across code and docs repos, plus optional resource directories (scripts/references/assets) for on-demand tasks.
  • Supports team governance workflows, PR/MR hygiene, and Obsidian-based documentation practices.

Quick Start

Use this skill when your current directory or an ancestor contains obsidian-docs to activate the team-collab protocol and begin guiding AI-assisted collaboration.

Frequently Asked Questions about team-collab-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize AI agent handoffs for team projects using Obsidian docs?

Standardize AI handoffs by encoding a team-project workflow protocol that governs Obsidian-docs-based state tracking and cross-repo collaboration. It maintains a state quartet of CURRENT/NEXT/RISKS/TODO and standardized handoff logs to ensure consistent agent behavior across code and docs repositories.

What is a state quartet in AI-assisted collaboration protocols?

A state quartet in AI-assisted collaboration protocols tracks project memory using CURRENT, NEXT, RISKS, and TODO fields. This frontmatter-driven mechanism maintains context across sessions, ensuring standardized handoffs and consistent agent behavior across code and docs repositories.

Does the team-collab-protocol skill require a specific directory structure to activate?

The skill requires a current directory or ancestor directory containing obsidian-docs to activate the protocol. It also enforces a strict metadata schema including name, description, dependencies, components, and toxicity checks, while supporting optional resource folders for scripts, references, and assets.

How do I maintain project memory across multiple code and docs repositories?

Maintain project memory across repositories by applying an end-to-end handoff protocol aligned with AGENTS.md references. It uses a frontmatter-driven skill unit identity and standardized handoff logs to synchronize agent behavior and governance workflows across separate code and docs environments.

What is the best way to govern PR/MR hygiene for AI-assisted documentation workflows?

Govern PR/MR hygiene by codifying team governance workflows that enforce a strict metadata schema and standardized handoff logs. This approach ensures consistent agent behavior and maintains frontmatter-driven skill unit identity across Obsidian-based documentation practices and cross-repo collaboration.