show-my-repo

Generate evidence-backed presentation packs from repository documentation and code.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ceasarXuu/AstartesSkills --skill show-my-repo-ceasarxuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: show-my-repo
Source: https://github.com/ceasarXuu/AstartesSkills/tree/main/skills/show-my-repo
Command: npx skills add https://github.com/ceasarXuu/AstartesSkills --skill show-my-repo-ceasarxuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a technical repository into a credible pitch for investors, users, or demos is hard: founders either overclaim or drown audiences in jargon. This Skill reads a repo's docs, code, and config, then produces a presentation pack where every claim is graded against actual evidence. ## Core Features & Use Cases - Evidence-Graded Packaging: Labels every claim as implemented, inferred, planned, or should-not-overclaim, with an evidence map linking claims to repo sources. - Audience-Specific Versions: Produces investor, user, and demo narratives plus 15-second and 60-second pitches from the same repo analysis. - Versioned Output Artifacts: Writes a structured presentation-pack.md to a dated, versioned output folder (show-my-repo/YYYYMMDD_vN/) for repeatable runs. - Use Case: A founder preparing for a demo day points the Skill at their repo and receives a fact sheet, architecture snapshot, highlight list, risk breakdown, and pitch scripts grounded in what the code actually does. ## Quick Start Analyze this repository and generate a complete investor-ready presentation pack with highlights, risks, and pitch versions saved to the output folder.

Frequently Asked Questions about show-my-repo

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

FAQPage Schema
How do I create an investor pitch from my GitHub repository?

Point the Skill at your repository and it reads the docs, code, and config to produce an investor version covering direction, painful workflow, implemented evidence, commercialization path, and current stage. Output is saved as a versioned presentation-pack.md file.

How to present a technical project to non-technical users?

The Skill generates a user version that is scenario-first and benefit-first with minimal jargon, plus a demo version with a 3-step demo path. It translates architecture into user-facing impact rather than listing technologies.

Does the repo presentation include unverified claims?

No. Every major claim is graded using an evidence rubric as implemented, inferred, planned, or should-not-overclaim, and an evidence map links each claim to its source. The Skill explicitly prohibits inventing traction, revenue, or usage data.

Where is the generated presentation pack saved?

Output is written to show-my-repo/YYYYMMDD_vN/presentation-pack.md at the repo root, where the date reflects the run day and vN increments if a folder for that date already exists. This keeps repeated packaging runs organized.

When should I not use repo-to-pitch packaging?

Avoid it when you only need bug fixing, code review, or internal API documentation, or when the repo is too incomplete to support any claims beyond speculation. The Skill requires enough evidence to separate implemented features from plans.