repo-portfolio-steering

name	repo-portfolio-steering
description	Generate a one-page portfolio steering report for workspace-hub. Use when the user invokes /repo-portfolio-steering, asks about harness vs engineering balance, wants a portfolio health check, or asks which repos to fund next. Reports on portfolio steering, GTM readiness, and provider activity balance.
version	1.0.0
category	workspace-hub
type	skill
trigger	manual
auto_execute	false
harness_threshold	0.3
capabilities	["harness_balance_check","gtm_readiness_ranking","provider_activity_analysis","next_actions_recommendation"]
tools	["Read","Bash","Glob"]
related_skills	["comprehensive-learning"]
scripts	["scripts/skills/repo-portfolio-steering/compute-balance.py"]
requires	[]
tags	[]

repo-portfolio-steering Skill

One-page portfolio steering report: harness/engineering balance, GTM-readiness ranking, per-provider agentic activity, and the next 3 highest-leverage actions to fund.

Quick Start

# Full steering report (run from workspace-hub root)
uv run --no-project python scripts/skills/repo-portfolio-steering/compute-balance.py

# Custom threshold
uv run --no-project python scripts/skills/repo-portfolio-steering/compute-balance.py --threshold 0.25

# With portfolio signals (Layer 2)
uv run --no-project python scripts/skills/repo-portfolio-steering/compute-balance.py \
  --signals .Codex/state/portfolio-signals.yaml

5 Output Sections

Section 1 — Balance Snapshot (L1)

Reads ## By Category summary table from INDEX.md.

Category	Count	%	Status
harness	N	N%	✓ / ⚠
engineering	N	N%	—

Threshold: harness_threshold in frontmatter (default 30%).

• ≤ threshold → HEALTHY

• threshold → OVER-INVESTED

Section 2 — Harness Saturation Signal

Layer 1 — Queue balance (from INDEX.md):

• Default threshold: 30% configurable via HARNESS_THRESHOLD
• Output: HEALTHY or OVER-INVESTED + recommended max harness items before returning to engineering

Layer 2 — Agentic activity by provider (from .Codex/state/portfolio-signals.yaml):

Provider | Harness (30d) | Engineering (30d) | Harness%
Codex   | 4             | 3                 | 57% ⚠ OVER
codex    | 1             | 5                 | 17% ✓
gemini   | 0             | 2                 | 0%  ✓

Source: portfolio-signals.yaml provider_activity section. If file is absent, Layer 2 is skipped (graceful degradation).

Layer 3 — Capability research (deferred to WRK-1020): key will be added by the nightly cron without breaking L1+L2.