portfolio-artifact

Collect and persist GTME portfolio metrics from local git and cost data.

28|3|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/ScientiaCapital/skills --skill portfolio-artifact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portfolio-artifact
Source: https://github.com/ScientiaCapital/skills/tree/main/active/portfolio-artifact-skill
Command: npx skills add https://github.com/ScientiaCapital/skills --skill portfolio-artifact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically capture and persist Go-To-Market Engineer portfolio metrics from development sessions, enabling visibility into ship rate, cost, and productivity across projects.

Core Features & Use Cases

  • Centralized metrics: commits, features, fixes, lines added/removed, tests added, cost, and derived metrics.
  • Weekly digests and executive summaries: generate leadership-ready reports and project dashboards.
  • End-to-end collection: daily end-of-day captures with storage at ~/.claude/portfolio/ and optional automatic weekly reports.

Quick Start

Run the portfolio artifact to capture today’s metrics and generate a weekly digest.

Frequently Asked Questions about portfolio-artifact

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

FAQPage Schema
How do I automate portfolio metrics collection for engineering projects?

Automate portfolio metrics collection by reading local git data and cost data to capture commits, features, fixes, and tests added. The process persists metrics to a configured storage path to produce standardized project dashboards.

Can I generate weekly executive summaries from development session data?

Generate weekly executive summaries by aggregating daily end-of-day captures of development session data. This creates leadership-ready reports detailing ship rate, cost, and productivity across projects.

What is the best way to track engineering costs and ship rate across multiple projects?

Track engineering costs and ship rate by centralizing derived metrics from git development sessions. This approach reads local cost data and git activity to calculate productivity metrics for centralized reporting.

Does this automated reporting approach require external dependencies?

No external dependencies are required to run this automated reporting approach. It operates independently by reading local git data, cost data, and configured storage paths to persist portfolio metrics.

Where are captured portfolio metrics stored for project dashboards?

Captured portfolio metrics are stored locally at a configured storage path, specifically the ~/.claude/portfolio/ directory. This local storage enables optional automatic weekly reports and standardized dashboard generation.