Agent skill
agent-ready-positioning
Make a product discoverable and purchasable when the buyer is an AI agent, not a human.
Filed under Positioning and messaging.
From vell-admin/gtm-skill-pack · 10 skills · 0 · pushed 2026-09-12
What it does when it runs
Make a product discoverable and purchasable when the buyer is an AI agent, not a human. Use when assessing or improving how an autonomous/agent buyer would find, evaluate, and transact your product.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- itsrondavis.com
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/vell-admin/gtm-skill-pack.git /tmp/gtm-skill-pack git -C /tmp/gtm-skill-pack sparse-checkout set "skills/agent-ready-positioning" mkdir -p ~/.claude/skills/agent-ready-positioning cp -R "/tmp/gtm-skill-pack/skills/agent-ready-positioning/." ~/.claude/skills/agent-ready-positioning/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from vell-admin/gtm-skill-pack/blob/1098b7c9837bc9ffba0e5614a957e0f335b9189d/skills/agent-ready-positioning/SKILL.md, which is licensed MIT (repository). 217 words, 4 headings.
Agent-Ready Positioning
Role. Act as an advisor on agentic commerce — making a product discoverable and purchasable when the buyer is an AI agent, not a human.
Ask the user for these inputs first
- Product + what it does in one plain sentence
- The task an agent would be doing when it should pick you
- Your data/integrations/APIs and how an agent would access them
- Pricing units and whether terms are machine-readable
If any are missing, ask one focused question rather than guessing.
Method
- Write a machine-legible product statement: what it is, the exact job it does, inputs/outputs, in unambiguous nouns (no metaphors).
- List the trigger tasks — when an agent is doing X, you are the right tool — phrased as an agent would query them.
- Audit discoverability: is your listing, docs, and pricing structured and parseable? Flag ambiguity an agent would trip on.
- Specify transactability: clear units, predictable cost, terms an agent can accept without a human.
- Give a checklist to become agent-ready, ordered by impact.
Output format
Return: the machine-legible statement, the trigger-task list, the discoverability flags, the transactability spec, and the ordered checklist.
© Ron Davis · AWS Marketplace GTM · Free to use. Want this run for you? https://itsrondavis.com/book-a-call
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- positioning-basics by BrianRWagner · 416
- positioning-and-story by AIDevGTM · 278
- crafting-positioning by GTM-Strategist · 255
- competitive-positioning by louisblythe · 153
- brand-messaging-and-positioning by manojbajaj95 · 100
- positioning-icp by chadboyda · 77
- positioning-map by pmalliance · 66
- portfolio-positioning by realjaymes · 60
Need help setting it up?
This page tells you what agent-ready-positioning does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.