Agent skill · Testing & QA

prompt-proximity-architecture

Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited canonical intent cells.

Elvis Sun613★ · +7/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add elvisun/newsjack --skill prompt-proximity-architecture --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/prompt-proximity-architecture/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 620 · +7 this week
Language: Go
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Prompt Proximity Architecture Design the cells before writing the strings. This skill inherits the ethical floor from `skills/ETHICS.md`. It enforces anti-hallucination and evidence-bound coverage. Anti-spray and human-send are not applicable. ## Inputs Require: - a measurement charter; - approved `icp_hypotheses.json` and `buyer_jobs.json`; - target run/review budget; - required locales, surfaces, and lanes; - any campaign partition and prior-panel constraints. If the charter is provisional, design a provisional architecture and name the gaps. Reject a charter that says only “track AI visibility.” ## Keep dimensions independent Each intent cell fixes: - buyer job; - information act; - journey state; - material constraints; - persona or buying role; - locale and language; - prompt-proximity band; - expected answer kind. Add independent tags for evidence grade, partition, lane eligibility, turn form, and optional funnel. Do not make funnel the schema. Use the supported acts `explain`, `diagnose`, `plan`, `generate`, `compare`, `recommend`, `verify`, `navigate`, `buy`, `implement`, and `troubleshoot`. Include only acts entailed by the job evidence. Use journey states `problem_ident

What's inside
Steps it walks through
  1. Inputs
  2. Keep dimensions independent
  3. Assign proximity
  4. Allocate coverage
  5. Prohibit unsupported cells
  6. Output
  7. Handoff
More from newsjack
All skills →
About this skill
What does the prompt-proximity-architecture skill do?

Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited canonical intent cells.

How do I install it?

Run `npx skills add elvisun/newsjack --skill prompt-proximity-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From elvisun/newsjack, a repository with 620 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going