skills.rest
venturecrane
venturecraneOFFICIAL
Explore all skills by this author →
GitHub

portfolio-review

Collect live portfolio signals and compare them against venture records.

Updated Jan 15, 2026
Search Tags:#github#portfolio#review#signals#drift#executive-summaries#production-url
One-click install
npx skills add https://github.com/venturecrane/crane-console --skill portfolio-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: portfolio-review
Source: https://github.com/venturecrane/crane-console/tree/main/.agents/skills/portfolio-review
Command: npx skills add https://github.com/venturecrane/crane-console --skill portfolio-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Portfolio data often drifts from reality as signals come in from development activity and deployments. This skill collects live signals, compares them to current portfolio records, and highlights changes for Captain approval.

Core Features & Use Cases

  • Collect live signals (GitHub activity, production URL health, VCMS executive summaries, and deployed resources) and surface drift against the portfolio.
  • Generate captain-ready review reports showing proposed status updates, bvmStage, and descriptions for each venture.
  • Use Case: Run a portfolio review quarterly to ensure the portfolio.json reflects current reality and triggers attention when drift is detected.

Quick Start

Run a portfolio review to collect signals, compare against records, and present changes for Captain approval.

Frequently Asked Questions about portfolio-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect portfolio drift from live GitHub activity and production URL health?▼

Detect portfolio drift by collecting live signals from GitHub activity, production URL health, and VCMS executive summaries, then comparing them against existing portfolio records to surface proposed status updates.

What is the best way to compare live deployment signals against existing portfolio records?▼

The best way to compare live deployment signals is to run a portfolio review that checks production URL health and Cloudflare resources against your records, generating a captain-facing report highlighting changes.

Do I need a config/ventures.json file to run a portfolio status review?▼

Yes, you need the config/ventures.json file because it serves as the single source of truth for ventures with showInPortfolio enabled during the portfolio status review.

How does drift detection work for venture bvmStage and description updates?▼

Drift detection works by collecting live signals like GitHub activity and comparing them to current portfolio records, highlighting proposed changes to bvmStage and descriptions for captain approval.

Can I generate executive summaries for ventures with showInPortfolio enabled?▼

Yes, you can generate captain-facing review reports that include VCMS executive summaries and proposed status updates specifically for ventures marked with showInPortfolio: true.

When should I run a portfolio review to check code health and deployed resources?▼

You should run a portfolio review quarterly to ensure your portfolio reflects current reality, checking code health and deployed Cloudflare resources to trigger attention when drift is detected.

Related Skills

Explore More Data & Analytics Skills→
concept2cureconcept2cure

design-tokens

Generate CSS variable and Tailwind design tokens for light and dark modes.

Community
Advanced
muklesmukles

git-commit-push-pr

Automate local changes into pull requests with adaptive descriptions.

Community
Intermediate
wodehwodeh

open-gstack-browser

Launch and monitor an AI-controlled Chromium browser with a live sidebar and activity feed.

Community
Intermediate
venturecraneventurecrane

enterprise-review

Audit cross-venture codebases to detect configuration and tooling drift.

Official
Advanced