jwa91/stackpicker
skills/stackpicker/SKILL.md
Advise on the stack for a new project. Given what the user wants to build, plus the user's principles and preferences, propose a language + tools as a short written proposal. Use when starting a new project or deciding what to build something in.
tools
Updated May 13, 2026
$ install --global
skillsauthnpx skillsauth add jwa91/agentskills stackpickerInstall 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: May 13, 2026, 7:25 AM195.0s3 files scanned
SKILL.md
- name:
- stackpicker
- description:
- Advise on the stack for a new project. Given what the user wants to build, plus the user's principles and preferences, propose a language + tools as a short written proposal. Use when starting a new project or deciding what to build something in.
- version:
- 0.1.0
Stack Picker
Assignment: given the user wants to create X, and given these principles and preferences, what stack would you advise for this new project? Present your advice as a short proposal back to the user.
Read both references before starting:
- references/principles.md — the user's tool-selection criteria and language-by-entrypoint defaults.
- references/decision-tree.md — the deterministic mapping from project shape to tools.
Always use the latest stable release of every tool. Do not pin or recommend version numbers. Always do some web research for the latest versions of important packages.
Steps
-
Decide what sort of project it is — language and surfaces.
- Match it against Phase 1 (language) and Phase 3 (surfaces) of the decision tree.
- New surfaces or hybrid project types are allowed. Fit them to the closest row in the tree and call that out in the proposal.
- This step also collapses the Phase 2 baseline (automatic, no question).
-
Decide which additional questions are relevant.
- Walk Phase 4, ask only the ones gated to this language / project. Skip any whose answer is implied by the description.
- Pick up ambient signals (secrets, dotfiles, App Store distribution, local LLM, n8n) from the description without asking.
-
Present a short proposal.
Free-form Markdown. Aim for a page or less. Cover, in this order:
- What we're building. One sentence echoing the user's intent.
- Stack at a glance. Language(s) + the surfaces being filled.
- Tools. One compact table grouping tools by what they do. Each row: tool, role, one short reason — citing a criterion from
principles.md(modern + fast, configurable, open standards, good DX, low memory, no vendor lock-in, agent-interactable) or a project-specific signal. - Anything new or off-list. If the tree had a gap (e.g. TUI for Go, TS API framework) or the project forced a deviation from the deliberately-not-on-the-table list, name it and the reason.
- Open questions. Honest unknowns the user should resolve before scaffolding.
No version numbers. No yes/no decision Docker rows; if Docker is in scope it's because "Add to VPS" was yes. No personal-environment tools (terminal, prompt, etc.).
Anti-patterns
- Asking about the language directly before trying to derive it from the description.
- Asking every Phase 4 question regardless of relevance.
- Producing a long structured report. The deliverable is a short proposal.
- Scaffolding code or running
initcommands. The deliverable is advice. - Recommending anything from
decision-tree.md's "Deliberately not on the table" list without a named constraint. - Pinning versions.
Related Skills
jwa91/release
data-ai
VerifiedTrustedCommunity
Release the current project to the personal Homebrew tap from repo-local release config. Use when the user says "release", "ship", "cut a version", "publish", "make a new tag", or asks how to make a new version available via jwa91/tap.
SKILL.mdUpdated May 14, 2026
jwa91/jwa-harden
tools
VerifiedTrustedCommunity
Use the `jwa-harden` CLI for secret-safe command execution, env-template discovery, and signing/notarization preflight checks. Trigger when a command needs secrets, when `.env.template` or 1Password references are involved, or before signed release flows.
SKILL.mdUpdated May 14, 2026
jwa91/tap-scaffolding
documentation
VerifiedTrustedCommunity
Modify or extend the `jwa-tobrew` scaffolding system — the templates that `init` writes into target projects. Trigger when the user says "add a new scaffold kind", "change what init writes", "update the templates", or asks how the embedded templates are wired.
SKILL.mdUpdated May 13, 2026
jwa91/tap-alignment
development
VerifiedTrustedCommunity
Detect and fix drift between a project and the conventions encoded in `jwa-tobrew`, prek, and the tap ADRs. Trigger when the user says "align", "any drift", "verify conventions", or asks why a particular file/symlink/script is required.
SKILL.mdUpdated May 13, 2026