Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
TPM Copilot
AI-powered operating system for Technical Program Managers and Project Managers. Pulls data from Jira, Linear, GitHub, and calendars to auto-generate status...
skill openclawclawhub Free
AI-powered operating system for Technical Program Managers and Project Managers. Pulls data from Jira, Linear, GitHub, and calendars to auto-generate status...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/jira-setup.md, references/linear-setup.md, references/report-templates.md, references/risk-categories.md, scripts/action-tracker.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- reighlan
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
TPM Copilot
Your AI program management operator. Pulls from Jira, Linear, GitHub, and calendars โ synthesizes everything into status reports, risk alerts, meeting prep, and stakeholder dashboards.
Dependencies
pip3 install requests For GitHub: install gh CLI and authenticate (gh auth login).
API Connections (configure in config.json)
Jira โ JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN (Atlassian API token) Linear โ LINEAR_API_KEY GitHub โ uses gh CLI (already authenticated) or GITHUB_TOKEN Slack โ SLACK_WEBHOOK_URL (for report delivery) Calendar โ iCal URL or Google Calendar API Not all required โ skill adapts to what's configured.
Workspace
tpm/ โโโ config.json # API keys, project settings, team config โโโ programs/ # Per-program data โ โโโ program-name/ โ โโโ config.json # Program-specific settings (board IDs, repos, teams) โ โโโ reports/ # Generated status reports โ โโโ risks/ # Risk register snapshots โ โโโ dependencies/ # Dependency maps โโโ templates/ # Report templates โโโ meetings/ # Meeting notes and action items โโโ state.json # Persistent state (last check timestamps, etc.) Run scripts/init-workspace.sh to create this structure.
1. Status Report Generator
The flagship workflow. Pulls from all connected tools, generates audience-specific reports. scripts/status-report.sh --program "my-program" --audience exec scripts/status-report.sh --program "my-program" --audience eng scripts/status-report.sh --program "my-program" --audience full scripts/status-report.sh --program "my-program" --audience exec --deliver slack Data pulled: Jira/Linear: sprint progress, tickets by status, velocity, blockers, recent completions GitHub: PRs merged/open/stale, CI status, release tags Calendar: upcoming milestones, meetings this week Audience formats: exec โ 3-5 bullet executive summary, RAG status per workstream, top risks, key decisions needed. Under 200 words. eng โ sprint metrics, PR review queue, blockers, velocity trends, upcoming deadlines full โ comprehensive program update with all sections, dependencies, action items Delivery options: stdout (default) โ prints to terminal slack โ posts to configured webhook email โ sends via Resend/SMTP confluence โ creates/updates a Confluence page file โ saves to programs/<name>/reports/
2. Risk & Blocker Radar
Proactive scanning for problems before they become crises. scripts/risk-radar.sh --program "my-program" scripts/risk-radar.sh --program "my-program" --alert # Send alerts for new risks scripts/risk-radar.sh --program "my-program" --history # Show risk trends Auto-detected risks: Stale tickets โ no updates in N days (configurable, default 5) Blocked tickets โ status = blocked, or flagged PR review bottlenecks โ PRs open >48h without review Sprint scope creep โ tickets added mid-sprint Missed commitments โ tickets rolled over from previous sprint CI failures โ broken builds on main branch Dependency delays โ upstream team's deliverables slipping Risk register maintained as JSON in programs/<name>/risks/: { "id": "RISK-001", "severity": "high", "category": "delivery", "title": "Auth service migration blocked on Team B API", "detected_at": "2026-02-24", "source": "jira_blocked_ticket", "ticket": "PROJ-1234", "status": "open", "mitigation": "", "owner": "" }
3. Meeting Autopilot
Automate meeting prep, notes processing, and follow-up tracking. scripts/meeting-prep.sh --program "my-program" --type standup scripts/meeting-prep.sh --program "my-program" --type sprint-review scripts/meeting-prep.sh --program "my-program" --type exec-sync scripts/meeting-prep.sh --program "my-program" --type program-review scripts/process-notes.sh --file meeting-notes.md # Extract action items scripts/action-tracker.sh --program "my-program" # Show overdue actions scripts/action-tracker.sh --program "my-program" --create-tickets # Create Jira tickets for actions Meeting types and auto-generated agendas: standup โ yesterday's completions, today's focus, blockers (from Jira) sprint-review โ sprint metrics, completed work, demos, carry-over items exec-sync โ program RAG, top risks, decisions needed, timeline status program-review โ full workstream status, dependencies, resource needs Notes processing: Parse markdown notes for action items (lines starting with AI:, TODO:, ACTION:, or [ ]) Extract owners and due dates Optionally create Jira/Linear tickets Track completion status across meetings
4. Dependency Tracker
Map and monitor cross-team dependencies. scripts/dependency-map.sh --program "my-program" # Generate dependency map scripts/dependency-map.sh --program "my-program" --check # Check for slips scripts/dependency-map.sh --program "my-program" --alert # Alert on at-risk dependencies Sources: Jira issue links (blocks/is-blocked-by) Jira/Linear labels (e.g., depends-on:team-b) Manual entries in programs/<name>/dependencies/deps.json Output: Markdown dependency table with status Critical path highlighting Alert when upstream dependencies slip
5. Program Dashboard
Quick terminal dashboard for program health. scripts/dashboard.sh --program "my-program" Shows: Overall RAG status Sprint progress (% complete, days remaining) Open risks by severity PR review queue Upcoming milestones Action items overdue
Program Config (programs/<name>/config.json)
{ "name": "Project Phoenix", "workstreams": [ { "name": "Backend", "jira_project": "PHX", "jira_board_id": "123", "github_repos": ["org/backend-api"], "team_lead": "Alice" }, { "name": "Frontend", "jira_project": "PHX", "jira_board_id": "124", "github_repos": ["org/web-app"], "team_lead": "Bob" } ], "milestones": [ {"name": "Alpha Release", "date": "2026-03-15", "status": "on-track"}, {"name": "Beta Release", "date": "2026-04-30", "status": "on-track"} ], "stakeholders": { "exec": ["vp-eng@company.com"], "eng": ["#eng-phoenix-slack-channel"], "full": ["phoenix-team@company.com"] }, "settings": { "stale_ticket_days": 5, "pr_review_threshold_hours": 48, "sprint_length_weeks": 2, "tracker": "jira" } }
Tracker Selection
Set settings.tracker to "jira" or "linear". Scripts auto-adapt API calls accordingly.
Cron Integration
Daily standup prep โ generate at 8:30 AM before standup Daily risk scan โ run at end of day, alert on new risks Weekly status report โ generate and deliver Monday AM Action item follow-up โ check overdue items daily Sprint boundary โ auto-generate sprint review data on last day of sprint
References
references/jira-setup.md โ Jira API authentication and project configuration references/linear-setup.md โ Linear API setup and GraphQL queries references/report-templates.md โ Customizing report formats and sections references/risk-categories.md โ Risk taxonomy and severity definitions
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
5 Docs1 Scripts
- SKILL.md
- references/jira-setup.md
- references/linear-setup.md
- references/report-templates.md
- references/risk-categories.md
- scripts/action-tracker.sh