repo-portfolio-steering
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.
Best use case
repo-portfolio-steering is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using repo-portfolio-steering should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/repo-portfolio-steering/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How repo-portfolio-steering Compares
| Feature / Agent | repo-portfolio-steering | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```bash # 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): `capability_signals` key will be added by the nightly cron without breaking L1+L2. ### Section 3 — GTM-Ready Technical Capabilities Ranks active engineering WRK items by demo-readiness: - Rank criteria: `brochure_status` (ready > updated > draft > n/a) - Secondary: `percent_complete` descending - Tertiary: WRK ID ascending (older = more considered) | WRK | Domain | Brochure | % Done | Demo Ready? | |-----|--------|----------|--------|-------------| ### Section 4 — Next 3 Actions to Fund Top 3 HIGH-priority engineering items mapped to GTM opportunities: | WRK | Domain | Client Persona | Project Type | Action | |-----|--------|---------------|--------------|--------| Domain → Client Persona → Project Type mapping: | Engineering Domain | Client Persona | Project Type | |---|---|---| | subsea pipeline / DNV RP F105 | Offshore operator / pipeline integrity engineer | VIV/freespan assessment | | cathodic protection | Corrosion engineer / asset manager | CP system design report | | marine / hydrodynamics | Naval architect / offshore designer | Motions & loads study | | drilling / ROP models | Drilling engineer / well planner | Drilling performance analysis | | production forecasting / Arps | Reservoir engineer / E&P consultant | Decline curve + reserves | | net lease / CRE | Real estate investor / asset manager | NNN lease underwriting | | structural / FEA | Structural engineer / EPC contractor | Plate/beam design check | ### Section 5 — Recommended Harness Budget Spend-rate formula based on current `harness_pct`: | harness_pct range | Budget rule | |---|---| | ≤ 15% | 1 harness per 3 engineering (ramp up harness) | | 15%–30% | 1 harness per 5 engineering (maintain) | | > 30% | 0 harness — pure engineering until below threshold | ## Runtime Inputs | Input | Path | Purpose | |---|---|---| | Category View | `.Codex/work-queue/INDEX.md` `## By Category` | Balance snapshot | | WRK frontmatter | `pending/*.md` + `working/*.md` | brochure_status, category, priority | | Portfolio signals | `.Codex/state/portfolio-signals.yaml` | L2 provider activity + L3 capability | ## Session-Start Integration This skill registers a **weekly steering mode** for `/session-start`: - Trigger: user invokes `/repo-portfolio-steering` OR session-start detects `--mode weekly` - Output replaces the "top items per category" summary with the full steering report - No changes to session-start SKILL.md body — steering invoked as a delegate ## Acceptance Criteria - [x] AC-1: SKILL.md at `.Codex/skills/workspace-hub/repo-portfolio-steering/SKILL.md` - [x] AC-2: Balance snapshot reads INDEX.md By Category - [x] AC-3: Harness threshold default 30% + configurable - [x] AC-4: GTM-readiness ranking by brochure_status + percent_complete - [x] AC-5: Next 3 to fund maps domains to client personas - [x] AC-6: Recommended harness budget outputs spend-rate - [x] AC-7: Harness saturation signal includes per-provider activity (Layer 2) - [x] AC-8: capability_signals key present does not crash (L3 compat) - [x] AC-9: Missing portfolio-signals.yaml graceful (no crash) - [x] AC-10: Session-start integration point documented - [x] AC-11: Description triggers on portfolio/steering/harness phrases
Related Skills
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
orcaflex-reporting-fixture-proof-pattern
Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
repo-separation-for-sensitive-data
Architecture pattern for splitting confidential data and reusable algorithms across repos
nested-git-repo-stash-safety
How to safely stash changes in a parent repo containing dirty nested git repositories
multi-repo-sync-diagnosis-repair
Diagnose and repair failed pulls across multi-repo ecosystems with stale locks, submodule conflicts, and untracked files
multi-repo-sync-diagnosis-and-repair
Systematic approach to diagnosing and repairing failures across a multi-repo workspace