adonis0123/repo-skill-creator
.agents/skills/repo-skill-creator/SKILL.md
Create and maintain repository skills for adonis-skills. Use when users ask to scaffold a new skill under skills/, generate agents/openai.yaml, run skill validation, refresh web index data, or standardize the skill authoring workflow.
$ install --global
skillsauthnpx skillsauth add adonis0123/adonis-skills repo-skill-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 6:11 PM61.3s5 files scanned
SKILL.md
- name:
- repo-skill-creator
- description:
- Create and maintain repository skills for adonis-skills. Use when users ask to scaffold a new skill under skills/, generate agents/openai.yaml, run skill validation, refresh web index data, or standardize the skill authoring workflow.
Repo Skill Creator
Create and maintain repository skills with a triple workflow: creation mode, path-finalize mode, and auto-discover finalize mode.
Trigger Rules
- If the user provides a
skills/*path and indicates the skill is already generated/copied, run path-finalize mode directly without additional confirmation. - If the user invokes this skill directly without providing a path, run auto-discover finalize mode (
skills:finalize:new) first. - If no new skill can be discovered during auto-discover mode, fall back to creation mode (
skills:new) and then continue finalize.
Mode A: Create New Skill
Primary command (recommended):
pnpm skills:new
Manual creation commands:
pnpm skills:init <skill-name> --path skills --resources scripts,references
pnpm skills:finalize -- skills/<skill-name>
Mode B: Finalize Existing Skill by Path
When the user pastes a path under skills/*, run:
pnpm skills:finalize -- <skill-path>
Examples:
pnpm skills:finalize -- skills/code-inspector-init
pnpm skills:finalize -- /Users/adonis/coding/adonis-skills2/skills/code-inspector-init/
Finalize pipeline is fixed and must run in order:
pnpm skills:quick-validate skills/<skill-slug>pnpm skills:validatepnpm skills:index
Mode C: Auto Discover + Finalize + Stage
When user does not pass a skills/* path, run:
pnpm skills:finalize:new
Behavior contract:
- Discover newly added skill candidates from
git status --short --untracked-files=all:- include
A(index-added) and??(untracked) - only accept slugs where
skills/<slug>/SKILL.mditself is inAor??
- include
- Finalize each discovered slug in stable sorted order:
pnpm skills:finalize -- skills/<slug>- stop immediately on first failure
- Stage only related files after all finalize runs succeed:
git add skills/<slug>for each processed sluggit add apps/web/src/generated/skills-index.jsonwhen changed
- If no new skill is discovered:
- auto-run
pnpm skills:new - re-scan for newly added skills and continue this mode
- auto-run
Scope Boundaries
- Do not auto-run
pnpm skills:openai-yamlunless explicitly requested. - Do not auto-run local install/sync (
skills:install:local,skills:test:local) unless explicitly requested. - Do not use
git add -A; only stage skill-related files from this workflow.
Output Contract
When executing this skill, always return:
- Commands executed (or planned commands in dry-run).
- Success/failure status.
- Detected/processed skill slugs and staged file paths.
- Next-step suggestion only when useful (for example, local agent testing via
pnpm skills:test:local).
Skill Rules
- Use lowercase hyphen-case skill names.
- Keep
SKILL.mdfrontmatter valid with non-emptynameanddescription. frontmatter.descriptionmust be English-only (ASCII characters only), and should clearly include when to use the skill.- Add optional directories (
scripts/,references/,assets/) only when needed. - Re-run validation and index generation after updates and before commit.
Related Skills
adonis0123/code-plugin-architecture
tools
VerifiedTrustedCommunity
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
2SKILL.mdUpdated May 30, 2026
adonis0123/workflow-gate
development
VerifiedTrustedCommunity
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.
2SKILL.mdUpdated May 17, 2026
adonis0123/agentic-review-handoff
development
VerifiedTrustedCommunity
Cross-agent code review handoff and review-fix-re-review loop with persistent packet artifacts. Requires a git repo because packet addressing uses git rev-parse --show-toplevel. Use when the user asks for an independent, read-only second pair of eyes on a diff/branch/PR another agent or teammate implemented; asks to verify reviewer feedback before fixing; says a fix is done and wants scoped re-review; asks to continue the latest review packet; or asks for first-principles, DDD, high-cohesion/low-coupling review. Persists each loop under $repo_root/.review-handoff/active/ so agents can resume without copy-paste. Do NOT use for ordinary implementation, generic staged-change review, review-comment copy editing, non-git folders/zips/tarballs/temp dirs, or when the user names a different review skill.
2SKILL.mdUpdated May 16, 2026
adonis0123/discuss-before-plan
testing
VerifiedTrustedCommunity
Enforces 'decide then plan' discipline - the pre-planning decision gate. Use when the user asks for a plan or starts a change while key decisions are unresolved: architecture tradeoffs, data flow, public interfaces, unclear requirements, multi-module scope, or roughly 5+ files affected. Also triggers when the user explicitly wants to discuss, compare options, or review architecture before committing. Core job: reduce incorrect-execution cost by confirming decisions before producing executable plans.
2SKILL.mdUpdated Mar 27, 2026