Latent Potential

First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this become", "is there a bigger play here", "how do I make this valuable or impactful", "assess this project", "strategic review", "where should t

49 stars 10 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add petekp/claude-code-setup --skill latent-potential
Manual install
git clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/latent-potential ~/.claude/skills/latent-potential

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Latent Potential

Walk into the project the way a hand-picked expert team would: a strategist, a positioning specialist, a product thinker, an architect, a distribution person, an ecosystem watcher, and a skeptic. The job is not to review the code. The job is to find value that is already latent in the project, name it precisely, and argue for the few moves that would channel it into something genuinely valuable and impactful.

"Latent" is the operative word. The best outcome of this exercise is not a clever idea the maintainer could chase. It is the discovery that they are already most of the way to something they have not noticed. Every recommendation should trace back to an asset that already exists.

## Principles

1. **Mechanisms, not labels.** Describe the project by what it actually does, not by its category. "A note-taking app" invites note-taking-app ideas. "A local-first sync engine with a markdown editor bolted on" invites uses no label would suggest, and reveals that the sync engine might be the product. First principles here means re-deriving what the thing is from its parts, then reasoning from that.
Read the full skill on GitHub

Details

Skill name
latent-potential
Path
skills/latent-potential/SKILL.md
License
MIT
Repo updated
26 October 2026

FAQ

What does the Latent Potential skill do?

First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this become", "is there a bigger play here", "how do I make this valuable or impactful", "assess this project", "strategic review", "where should t

How do I install the Latent Potential skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill latent-potential. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Latent Potential popular?

It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.

Related skills

Catch Up

49

petekp/claude-code-setup

Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.

AI, LLMs & Agents10

Clean Copy

49

petekp/claude-code-setup

Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.

Writing & Content10

Code Comments

49

petekp/claude-code-setup

Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.

Software Development10

Dayz Modding

23

StarDZ-Team/Dayz-Modding-Skills

ALWAYS use when touching ANY DayZ file (.c, config.cpp, mod.cpp, .layout, types.xml) or discussing DayZ modding, Enforce Script, or the Enfusion engine. Activate even if the user does not explicitly mention DayZ — if the code imports DayZ classes (PlayerBase, EntityAI, ItemBase, MissionServer), uses DayZ APIs (GetGame(), Class.CastTo(), ScriptRPC), or references DayZ patterns (modded class, CfgPatches, requiredAddons), this skill MUST be loaded. Covers 40+ critical gotchas, complete engine API across 20+ systems, mod architecture, RPC networking, GUI widgets, performance optimization, and prof

Software Development11

Exhaustive Systems Analysis

49

petekp/claude-code-setup

Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.

Software Development10

Nuxt Best Practices

43

vinayakkulkarni/vue-nuxt-best-practices

Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications. This skill should be used when writing, reviewing, or refactoring Nuxt code to ensure optimal patterns. Triggers on tasks involving data fetching, server routes, auto-imports, rendering modes, layouts, named views, or Nuxt-specific features.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.