CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-spark-stress-prfaq

This skill should be used when the user says "prfaq", "pr faq", "pr/faq", "press release stress test", "stress prfaq", "amazon pr faq method", "test the pitch with a pr/faq", "validate concept through pr/faq", "critique press release", "pr faq stress test", "will this marketing story hold up", or wants to stress-test a product concept by drafting a compelling press release and FAQ, then adversarially critiquing it to find where the concept cracks under scrutiny. Produces a PR/FAQ report with the full draft, adversarial questions, crack point analysis, and recommended concept updates.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a well-sequenced workflow, explicit validation checkpoints, and clean one-level reference structure. Its only weakness is conciseness: rationale prose is duplicated between the body and the workflow reference.

Suggestions

Remove the 'two phases use separate agent invocations to prevent rubber-stamping' rationale paragraph from the SKILL.md body since the same rationale already lives in references/prfaq-workflow.md's 'Rationale for Separate Invocations' section; keep only the operational requirement in the body.

Consolidate the duplicated draft/critique quality-check and retry criteria that appear in both the body and prfaq-workflow.md so each lives in one place, with the body briefly pointing to the reference for full criteria.

DimensionReasoningScore

Conciseness

The body is mostly efficient but re-explains rationale ('A critic who remembers being the drafter unconsciously defends what it wrote. Separate invocations force genuine adversarial evaluation.') that is duplicated in prfaq-workflow.md's 'Rationale for Separate Invocations' section, so it could be tightened rather than reaching the lean top anchor.

2 / 3

Actionability

Provides copy-paste-ready guidance — exact context-block delimiters ('--- PRODUCT CONCEPT ---'), quoted retry prompts, word-count targets (400-600), concrete quality-check criteria, and AskUserQuestion option lists — fully executable rather than the pseudocode/vague mid-anchors.

3 / 3

Workflow Clarity

Steps 1-6 are clearly sequenced with explicit quality-check checkpoints after the draft (Step 3) and critique (Step 4), retry feedback loops, and a dedicated Error Handling section, matching the 'clear sequence with explicit validation steps' top anchor.

3 / 3

Progressive Disclosure

The overview body signals two real one-level-deep references (prfaq-workflow.md and prfaq-report-template.md, both verified present) with clear Read paths and no deep nesting, matching the 'clear overview with well-signaled one-level-deep references' top anchor.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it names concrete actions, supplies a wide range of natural trigger phrases, explicitly covers both what and when, and occupies a distinctive niche unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'drafting a compelling press release and FAQ, then adversarially critiquing it' and 'Produces a PR/FAQ report with the full draft, adversarial questions, crack point analysis, and recommended concept updates' — matching the top anchor rather than the vague mid-level 'names domain and some actions'.

3 / 3

Completeness

Explicitly answers both what (stress-test a concept by drafting a PR/FAQ then adversarially critiquing, producing a report) and when ('This skill should be used when the user says...'), with explicit triggers capping above the score-2 'has what, when implied' anchor.

3 / 3

Trigger Term Quality

Broad coverage of natural phrasings a user would say — 'prfaq', 'pr faq', 'pr/faq', 'press release stress test', 'amazon pr faq method', 'will this marketing story hold up' — well beyond the 'some relevant keywords' mid-anchor.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Amazon PR/FAQ stress test) with distinctive trigger terms unlikely to fire for other skills, matching the 'clear niche with distinct triggers' top anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AppsVortex/arness
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.