PMO assistant for a running IKANGAI Signals instance: month-end closure driving, portfolio health briefings, capacity checks, and compliance chasing — via a bundled remote MCP connector (OAuth), no CLI required. Works in Claude Code and Claude Desktop.
Plugin pmo from marketplace ikangai in ikangai/claude-plugins. Commands read from the repo's manifest — 12 days ago.
briefingPortfolio health briefing for IKANGAI Signals. Use for "how's the portfolio", "status report", "portfolio briefing", "which projects need attention" — collects financials, YTD variance, risks, AR aging, capacity and closure state across projects, ranks by attention-worthiness, and reports. Optional
capacityResource capacity and over-allocation check for IKANGAI Signals. Use for "who's over-allocated", "capacity check", "staffing gaps", "allocation vs actuals" — analyzes the planned-vs-actual allocation matrix for over-allocations, allocation cliffs, and plan/actual divergence. Argument is the year (de
chaseCompliance chasing for IKANGAI Signals — missing timesheets and overdue invoices. Use for "who hasn't submitted timesheets", "chase list", "overdue invoices", "AR follow-up". Produces a per-person / per-customer chase list with copy-ready nudge messages (v1 drafts only, does not send). Argument is t
closuresMonth-end closure driver for IKANGAI Signals. Use for "run month-end", "closure status", "what's ready to approve", "sweep closures" — sweeps the portfolio for a month, buckets projects (missing/open/locked/approved), collects blockers, presents an approve/reject decision table, and can create missi
signals-operatingFoundation for operating a IKANGAI Signals instance through the bundled remote MCP connector. Load FIRST from any workflow skill of the pmo, pm or employee plugin, or whenever calling IKANGAI Signals — the connector tools, auth/preset preflight, error decoding, context-lean reads, the write-safety t
pmo-collectorRead-only IKANGAI Signals data collector. Give it how to call the connector's tools, an explicit list of read-only signals_call commands, and the output shape; it calls them exactly as specified and returns one compact JSON object. Never writes, returns per-command errors as data instead of failing.
signalsconnects to: https://signals.ikangai.com/mcp
A self-organizing polity of parallel AI coding-agent sessions on one repo — coordinate via hooks, @mentions, a (per-squad) team barrier, a task ledger, fan-in, a hub-and-spoke lead, an advisory constitution + parliament, cross-CLI bridges, and token tracking. (Formerly groupchat.)
1 skill · 25 commands · hooks
Self-service assistant for a running IKANGAI Signals instance: book and submit your timesheet, request leave, file expenses, and see what's on your plate — via a bundled remote MCP connector (OAuth), no CLI required. Works in Claude Code and Claude Desktop.
5 skills · 1 MCP server
Project-manager assistant for a running IKANGAI Signals instance: project status, month-end closure prep and lock, timesheet and expense approvals, and keeping risks, issues, actions and decisions current — via a bundled remote MCP connector (OAuth), no CLI required. Works in Claude Code and Claude Desktop.
5 skills · 1 MCP server
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.