agentsclimarketplace

Product context

Skill markoblogo/abvx-agent-skills/skills/product-context

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install
npx -y skills add markoblogo/abvx-agent-skills --skill product-context

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build or refresh a compact, evidence-backed product context before marketing, positioning, SEO, analytics, sales-enablement, or launch work. Use when an agent needs to understand the product, audience, proof, conversion goal, terminology, and claim boundaries without inventing commercial facts.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, as published. Nobody here has run it

Product Context

Create a small, durable context artifact that lets later product work start from evidence instead of generic positioning.

Use When

  • entering marketing, content, SEO, analytics, sales, or launch work in a repo;
  • the product, audience, conversion action, or proof boundary is unclear;
  • existing public copy and internal product behavior have drifted.

Workflow

  1. Read existing product docs, public copy, analytics contracts, and relevant implementation surfaces.
  2. Separate confirmed facts from assumptions, placeholders, and claims needing owner confirmation.
  3. Draft or update docs/product-context.md unless the repo already defines a better canonical path.
  4. Keep only: product and audience, jobs and conversion action, terminology, proof and known limits, approved voice, prohibited claims, source surfaces, and last-reviewed date.
  5. Ask for confirmation where positioning, ICP, pricing, competitor claims, or proof cannot be established from the repo.
  6. Link future work to the context; do not treat it as permission to publish, spend, contact people, or change product behavior.

Guardrails

  • Never invent customer quotes, metrics, market position, availability, pricing, partner status, or legal/compliance claims.
  • Keep personal data and private sales evidence out of a committed context file.
  • Treat a product context as a reviewable input, not a source of truth over code, current policy, or human direction.
  • Preserve domain-specific safety language such as financial, booking, or approval boundaries.

Output Shape

Use these headings where applicable: Product, Audience and jobs, Conversion action, Proof and limits, Language, Claim boundaries, Source surfaces, Maintenance.

Pair With

  • evidence-ledger-research for external facts;
  • social-publishing-gate before distribution;
  • bounded-growth-loop before recurring optimization;
  • loop-readiness-review before scheduling any loop.

Provenance

Adapted from the shared-context architecture in coreyhaines31/marketingskills, narrowed to evidence-backed, product-neutral context with explicit claim boundaries.

Gives 0 of the 12 instructions most product growth skills give

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 24 of 728, across 15 files
  • define the ideal customer profilein 21 of 728, across 3 files
  • document a rollback plan before deploymentin 21 of 728, across 12 files
  • analyze the codebase to understand the productin 19 of 728, across 1 file
  • ask clarifying questions about the value propositionin 19 of 728, across 1 file
  • search for companies matching the criteriain 19 of 728, across 1 file
  • look for signals of immediate needin 19 of 728, across 1 file
  • assign a fit score from one to tenin 19 of 728, across 1 file
  • identify the target decision maker rolein 19 of 728, across 1 file
  • suggest a personalized contact strategyin 19 of 728, across 1 file
  • provide conversation starters for outreachin 19 of 728, across 1 file
  • format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

  • Read existing product docs and implementation surfaces
  • Draft or update the product context file
  • Keep only product, audience, proof, terminology, and limits
  • Ask for confirmation where proof cannot be established
  • Link future work to the context

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.