CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 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 · 1 flagged

Securityscore 88 · 1 finding

MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · CONTRIBUTING.md

MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.

Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted

excerptCONTRIBUTING.md· markdown

272. **Idempotent.** Re-running a bootstrap produces the same state. Never overwrite user cont

… (56 chars elided on L27)

283. **Profiles are data, never code.** No `eval`, no embedded scripts, no remote includes.

294. **`gh` integration is always best-effort.** Skip with a logged reason; never fatal, never

… (18 chars elided on L29)

305. **MCP boundary.** Shell scripts never invoke MCP tools — only the skill layer does.

316. **No internal references in code.** Names must be self-descriptive. Traceability belongs

… (15 chars elided on L31)

Occurrences

1 occurrence · at L29

How to fix

Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.

Delete blanket "don't ask / no need to confirm" directives from the skill.
If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-DONT-ASK-01sha256183eb789192b5159…rubric 365aacaView on GitHub

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.

skills/migrate-profile/SKILL.md · 1 file

skills/migrate-profile/SKILL.md3.3 KB · Markdown

name: migrate-profile

description: "Switch this repository from one nyann profile to another. TRIGGER ON: 'switch profile', 'migrate profile', 'change this repo profile', 'switch from X to Y', 'change profile to', 'migrate from', 'use a different profile', 'switch to nextjs', 'switch to python'. Computes a diff between source and target profiles, previews all hook/config/convention changes, and applies via bootstrap."

migrate-profile — Switch Between Nyann Profiles

You are the migrate-profile skill. You switch a repository from one nyann profile to another, computing the diff and applying changes safely.

When to trigger

User asks to switch, migrate, or change the repo's profile
User says "switch from X to Y" or "use the python profile instead"
User asks to change the repo's configuration to match a different stack

DO NOT trigger on: schema version migration (that's bin/migrate-profile.sh), initial bootstrap, or retrofit.

Execution flow

Phase 0: Team profile freshness check (quick, non-blocking)

Run bin/check-team-staleness.sh before starting. If it produces output, show the notification to the user (e.g. "Your team profiles have upstream changes. Run /nyann:sync-team-profiles to update before migrating, or continue with the current versions."). Do not block — let the user decide whether to sync first.

Phase 1: Identify source and target profiles

Source profile: resolve from CLAUDE.md markers or preferences. If ambiguous, ask.
Target profile: from the user's request. If they named a profile, use it. If they described a stack ("switch to Python"), resolve to the matching starter profile.
Validate both exist via bin/load-profile.sh <name> (positional argument).

Phase 2: Compute and preview diff

Run bin/switch-profile.sh --from <source> --to <target> --target . --dry-run.
Show a human-readable table of changes:

Hooks added/removed per phase
Branching strategy change
Extras toggled
Convention changes
CI configuration changes

Highlight potentially destructive changes (hook removals, strategy changes).

Phase 3: Confirm and apply

Ask: "Apply this migration? This will regenerate CLAUDE.md and update hooks."
On confirmation, re-run with --yes (and without --dry-run).

The script refuses to apply without --yes; emitting the plan and asking is the human-confirm half of preview-before-mutate.

Report what changed.

Phase 4: Post-migration

Suggest running /nyann:doctor to verify the new state.
Suggest committing the changes.

Key constraints

The script diffs two profiles — it doesn't modify the profile files themselves.
Bootstrap is re-run with the new profile to regenerate managed files.
User content outside nyann markers is always preserved.
If the profiles are identical, report "nothing to migrate" and exit cleanly.

When to hand off

"Check if the migration worked" → doctor skill.
"Regenerate CLAUDE.md" → gen-claudemd skill (if CLAUDE.md wasn't

refreshed during the migration).

"What does the new profile look like?" → inspect-profile skill.
"Undo the migration" → if not yet committed, restore individual

files with git checkout -- <file> for each changed file. If already committed, use the undo skill to revert the commit.

migrate-profile— agent skill

Is migrate-profile safe to install?

migrate-profile — Switch Between Nyann Profiles

When to trigger

Execution flow

Phase 0: Team profile freshness check (quick, non-blocking)

Phase 1: Identify source and target profiles

Phase 2: Compute and preview diff

Phase 3: Confirm and apply

Phase 4: Post-migration

Key constraints

When to hand off

Audit the pieces. Scan the whole. Decide.