Skills by risk · page 110
Highest-trust agent skills
9,826 skills rated SAFE with grade A or B, best score first. All are grade B today: grade A needs a sandboxed run we do not do for skills yet. Ties are broken by stars, so a repository with many skills can fill a page.
Cite
Cite this page
ModelsAtlas. “Highest-trust agent skills”. Retrieved 30 Oct 2026. https://modelsatlas.com/skills/trusted/page/110
deanpeters/Product-Manager-Skills
Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.
deanpeters/Product-Manager-Skills
Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.
deanpeters/Product-Manager-Skills
Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.
deanpeters/Product-Manager-Skills
Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.
deanpeters/Product-Manager-Skills
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
deanpeters/Product-Manager-Skills
Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.
deanpeters/Product-Manager-Skills
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
deanpeters/Product-Manager-Skills
Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.
deanpeters/Product-Manager-Skills
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.
deanpeters/Product-Manager-Skills
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
deanpeters/Product-Manager-Skills
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
deanpeters/Product-Manager-Skills
Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.
deanpeters/Product-Manager-Skills
Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation.
deanpeters/Product-Manager-Skills
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
deanpeters/Product-Manager-Skills
Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.
deanpeters/Product-Manager-Skills
Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.
deanpeters/Product-Manager-Skills
Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards.
tw93/Waza
Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.
tw93/Waza
🥷 Engineering habits you already know, turned into skills Claude can run.
tw93/Waza
Finds root cause before any fix. Use when something errors, crashes, regresses, or used to work. Not for code review or new features.
tw93/Waza
Runs a six-phase research workflow from source bundle to publish-ready output. Use when researching an unfamiliar domain or compiling materials into one reference. Not for quick lookups or single-file reads.
tw93/Waza
Fetches URLs and PDFs, then summarizes or returns clean Markdown. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.
tw93/Waza
Turns rough ideas into approved, decision-complete plans before coding. Use when planning architecture, judging whether to build, or writing a handoff. Not for bug fixes or small edits.
tw93/Waza
Rewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.