Product Agent Skill
Create or refine PRODUCT.md while separating evidence, aspiration, users, value, and non-goals. Triggers: "product", "create PRODUCT.md", "product boundary".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/boshu2/agentops --skill productThe instruction itself
1 sections, as written by the authorProduct
Create or refine a product contract with the user's authority.
The contract works because it forces every claim into evidence or labeled
aspiration; if a reader cannot tell which is which, the document has failed.
- Inspect existing product, README, goals, release, and evidence sources.
- Ask only for decisions that cannot be grounded safely from those sources.
- State mission, users, pains, value, differentiation, and non-goals.
- Separate evidence from hope under two required headings. Put every grounded
claim under ## Proven, each carrying a resolvable citation (a README,
release, test, or evidence source). Put unproven hopes, evidence gaps, and
not-yet-measured success signals under ## Assumptions. A claim that cannot
cite a source belongs under ## Assumptions, never ## Proven.
- Preserve an existing PRODUCT.md unless the user authorizes replacement.
- Return the document to the caller; Plan may use it as intent context.
Named failure mode — aspiration laundering: an unproven hope written in the
## Proven section; once laundered, every downstream plan inherits a false
premise. Detector: any ## Proven claim without a resolvable citation is a
laundered aspiration — move it to ## Assumptions or cite it.
Anti-pattern: rewriting a healthy PRODUCT.md wholesale because the session has
fresh opinions. Corrective: refine only the sections the user asked to change
and preserve the rest byte-for-byte.
Product does not select work, invoke a loop, repair itself, validate itself, or
choose delivery.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take boshu2/product from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.