A product-identity audit for checking what a product does, who it serves, and whether its features support its main purpose. It compares product context, features, users, workflows, and competitors.

Use it after a product pivot, when the product feels unfocused, or before strategic planning to review its positioning and feature direction.

It helps reveal when a product has accumulated unrelated features or when its description no longer matches what it actually offers. This gives planning a clearer basis.

How VGrss/Acumen configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to VGrss/Acumen. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/VGrss/Acumen/main/.agents/skills/orientation/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/VGrss/Acumen

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vgrss/acumen/orientation/github.svg)](https://agentmods.dev/skills/vgrss/acumen/orientation)

Your own site

<a href="https://agentmods.dev/skills/vgrss/acumen/orientation"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/orientation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vgrss/acumen/orientation"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/orientation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,873 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.01873
Opus 5.5	$0.00023	$0.00749
Sonnet 5.5	$0.00012	$0.00375
Haiku 4.5	$0.00006	$0.00187

Measured 2mo ago against content hash 1d742fe6379a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orientation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/orientation/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MANDATORY PREPARATION

Invoke /product-thinking — it contains the Context Gathering Protocol and the AI Slop Test. Follow the protocol before proceeding.

Mindset

Most products drift. Features accumulate because customers asked, competitors shipped, or someone had a slow week. Over time, the product says it does one thing but actually does twelve — and none of them well enough to be the reason someone chooses it.

Orientation is the audit that catches drift. You are not here to validate. You are here to hold a mirror up and ask: does the product we built match the product we say we are?

Context Pull

Load everything. This is a read-heavy skill:

Product context. Read .acumen.md — positioning, thesis, stage, target users, strategy.
Feature inventory. Read .acumen/features.md — every capability the product has today.
Personas. Read .acumen/personas.md — who we say we serve, and their behaviors.
Value chain. Read .acumen/value-chain.md — the end-to-end workflow per persona. Use this to check whether features align with the steps where we claim to bring value.
Competitors. Read .acumen/competitors.md — how the market frames us vs. alternatives.

If any context file is missing, flag it. Orientation without a feature inventory or personas is guesswork.

Core Protocol

1. Thesis Check

State the product thesis in one sentence. Then ask:

Can every feature in the inventory be traced back to this thesis?
Which features serve the thesis directly? Which serve it indirectly? Which don't serve it at all?
If you removed the orphan features, would anyone notice? Would retention change?

Features that don't connect to the thesis are either: (a) the thesis is wrong and needs updating, or (b) the feature is drift and should be deprecated or spun out.

2. Persona Alignment

For each primary persona in .acumen/personas.md:

Which features serve this persona's core job?
Which features are irrelevant to them (clutter)?
Is there a gap — a job this persona needs done that the product doesn't address?
Value chain coherence — Do the features we built match the steps we claim to own in .acumen/value-chain.md? Are there chain steps marked as "Own" with no corresponding feature, or features with no chain step?
Would this persona describe the product the same way the positioning does?

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 135 lines · 58 tokens per session scan A 1d742fe6379a

Subscribe to this mod's changes

orientation is a skill published in the GitHub repository VGrss/Acumen (12 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,873 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Marketing and SEO Planning

orientation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
orientationVGrss/Acumen	Skill	12	3mo ago	Apache-2.0	A	58	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

Acumen: Skill for Claude Code