vibe-what-do-i-want 100/100

Is vibe-what-do-i-want safe to install?

SaferSkills independently audited vibe-what-do-i-want (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

bundled/skills/vibe-what-do-i-want/SKILL.md · 1 file

bundled/skills/vibe-what-do-i-want/SKILL.md1.5 KB · Markdown

name: vibe-what-do-i-want

description: Clarify intent and freeze requirements by entering the canonical vibe runtime with a discovery-first bounded stop.

Use canonical vibe as the only governed runtime authority for this request.

Entry bias:

clarify what the user actually wants
shape scope before solutioning
strengthen requirement-first discovery
stop after canonical requirement_doc

Execution rules:

delegate to canonical vibe
keep vibe as the only runtime authority
let canonical vibe keep router selection and confirm_required ownership
do not create a second requirement surface
do not create a second plan surface
do not create a parallel runtime
do not preflight-scan the current workspace or repository for canonical proof files before launch
Launch canonical-entry first; validate receipts only after it returns a session root
do not continue into xl_plan, plan_execute, or phase_cleanup unless the user explicitly re-enters through canonical vibe or another approved wrapper
when a later wrapper intentionally continues from this bounded stop, forward --continue-from-run-id <source_run_id> and --bounded-reentry-token <reentry_token> from the latest runtime-summary.json bounded_return_control block

When this wrapper is chosen, enter canonical vibe with:

stronger deep_interview
stronger requirement clarification before planning
a bounded terminal stage of requirement_doc

Request: $ARGUMENTS

vibe-what-do-i-want— agent skill

Is vibe-what-do-i-want safe to install?

Audit the pieces. Scan the whole. Decide.