Skip to content
TrustedSkillsbeta
Back to all skills

Prd Implementation Precheck

Checked
charon-fan·vlatest·productivity·MIT

This skill swiftly analyzes product implementation plans to identify potential roadblocks and ensure a smoother launch, boosting productivity.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add zhaono1/agent-playbook --skill prd-implementation-precheck -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

charon-fan

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned charon-fan/agent-playbook at be7a9d7d17.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 210 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps ensure a product implementation is ready to proceed by systematically checking key prerequisites. It assesses aspects like stakeholder alignment, technical feasibility, and resource availability. The goal is to identify potential roadblocks early on, minimizing risks and ensuring a smoother launch.

When to use it

  • Before kicking off a new product feature development cycle.
  • When transitioning from the planning phase to implementation for a product.
  • To proactively mitigate risks associated with launching a new product or feature.
  • During a go/no-go decision point before significant investment in implementation.

Key capabilities

  • Stakeholder alignment assessment
  • Technical feasibility validation
  • Resource availability verification
  • Risk identification and mitigation planning

Example prompts

  • "Run a precheck for the new customer onboarding flow."
  • "What are the key risks we should consider before starting implementation of the mobile app redesign?"
  • "Generate a checklist to ensure all prerequisites are met for launching version 2.0."

Tips & gotchas

This skill is most effective when used early in the product development lifecycle, ideally during the planning phase. It assumes access to relevant documentation and stakeholder availability for assessment.