cog-team-intelligence
npx machina-cli add skill a5c-ai/babysitter/team-intelligence --openclawFiles (1)
SKILL.md
1.6 KB
COG Team Intelligence Skill
Cross-reference GitHub, Linear, Slack, and PostHog data to generate unified team intelligence briefs with bidirectional sync support.
Capabilities
- Gather activity data from GitHub (PRs, issues, commits, reviews)
- Gather activity data from Linear (issues, cycles, projects)
- Gather activity data from Slack (discussions, decisions, threads)
- Gather analytics from PostHog (metrics, feature flags, experiments)
- Cross-reference data across all platforms
- Detect cross-platform misalignment
- Generate team intelligence briefs with blocker detection
- Support bidirectional sync between platforms
Tool Use Instructions
- Use
api-callorweb-fetchto gather data from configured integrations - Normalize data from each platform into comparable format
- Cross-reference to identify patterns spanning platforms
- Use
file-readto load existing team context from 04-projects - Use
file-writeto create team brief in 01-daily - Use
file-writeto update team context in 04-projects - Use
git-committo commit team intelligence
Examples
{
"vaultPath": "./cog-vault",
"mode": "team-brief",
"userName": "Alex",
"integrations": {
"github": { "org": "my-org", "repos": ["frontend", "backend"] },
"linear": { "team": "engineering" },
"slack": { "channels": ["engineering", "product"] }
}
}
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/cog-second-brain/skills/team-intelligence/SKILL.mdView on GitHub Overview
COG Team Intelligence cross-references data from GitHub, Linear, Slack, and PostHog to generate unified team briefs with bidirectional sync. It detects cross-platform misalignment and blockers, delivering actionable insights for engineering and product teams.
How This Skill Works
The skill uses api-call or web-fetch to gather data from configured integrations, normalizes data into a common schema, and cross-references patterns across platforms. It then loads existing context from 04-projects, writes the new team brief to 01-daily, updates the project context, and commits changes with git-commit.
When to Use It
- To produce a consolidated briefing across GitHub, Linear, Slack, and PostHog for daily standups or leadership reviews
- To identify cross-platform misalignment and root cause blockers before planning
- To surface cross-platform trends (PRs, issues, Slack decisions, PostHog metrics) for sprint retros
- To refresh team context by syncing 04-projects with 01-daily briefs
- To automate documentation and sharing of team intelligence with version control commits
Quick Start
- Step 1: Use api-call or web-fetch to gather data from configured integrations
- Step 2: Normalize data from each platform into a comparable format
- Step 3: Cross-reference to identify patterns across platforms, load context from 04-projects, write to 01-daily, commit via git-commit
Best Practices
- Normalize data into a common schema before cross-referencing
- Validate time frames and data freshness across sources
- Keep integration configs explicit (repos, channels, team names) to avoid drift
- Include blocker and alignment flags in briefs for quick actions
- Use git-commit to record team intelligence with clear, meaningful messages
Example Use Cases
- Engineering team receives a daily cross-platform brief highlighting open PRs, cycles, Slack decisions, and feature flags to guide the day
- A major feature release triggers a cross-platform alignment check, surfacing misalignments between GitHub issues and Linear workflows
- A quarterly team health digest combines activity from GitHub, Linear, Slack, and PostHog for leadership review
- Sprint planning is boosted by a cross-platform briefing that surfaces blockers from issues, threads, and experiments
- Incident response coordination is improved by a cross-platform summary that links Slack decisions, code changes, and telemetry
Frequently Asked Questions
Add this skill to your agents