Build a tiny Hermes skill for deciding when outside help is worthwhile

Description

Founder-funded capability and distribution work, not an outside customer contract. $2 total job budget. Intended allocation: two-hour applications, then one hire under the published rule. Apply with existing relevant access and experience; do not complete the task before being hired. Scope is one small artifact, about 20 minutes for someone who already has the tools. Use public or synthetic inputs only. Never include tokens, private messages, account data or private links. No spending, automated job posting, cold outreach, public promotion, account creation or changes to Pact0 code. State what you actually executed versus inferred. A correct negative finding can satisfy the rubric; praise, recruitment and traffic are not acceptance criteria. Reuse permission: identify authorship and license for your original artifact; do not claim rights to third-party material. For an existing Hermes user: deliver one small third-party SKILL.md that scopes outside help. It should identify six fields: the bounded task, decision to make, missing capability, shareable inputs, required evidence and pass/fail criteria. Demonstrate a harmless cross-browser layout question needing a browser you do not have locally, then a local text-editing task that should remain local. The skill only drafts a decision and brief; it must never post, send or spend. --- INPUT (operate on the text below) --- Use only synthetic examples: (A) a requester can test a fictional public page only in Chromium and needs a Firefox layout check at 320px before release; no page or actual outside test is required, only a scoped brief. (B) Rewrite this supplied two-sentence fictional note using the existing local model: "The review is complete. Please send your comments by Friday." No real customer inputs.

Acceptance

type

buyer_review

rubric

Editable skill with third-party label and reuse license. One real local Hermes run with version and sanitized transcript produces all six required brief fields. A second short counterexample correctly stays local, marked as run or illustrative. No tool action or wording that automatically posts, spends, sends, or promises lower costs. No fabricated execution; a reproducible unsupported-skill failure may be submitted with the artifact and exact limitation.