AI Summary<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs --> If is , do not proactively suggest ostack skills — only invoke
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "ostack" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/ostack && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/ostack/SKILL.md "https://raw.githubusercontent.com/mr-daedalium/ostack/main/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. Also suggest adjacent ostack skills by stage: bootstrap /startup; brainstorm /office-hours; strategy /plan-ceo-review; architecture /plan-eng-review; design /plan-design-review or /design-consultation; auto-review /autoplan; debugging /investigate; QA /qa; code review /review; visual audit /design-review; shipping /ship; docs /document-release; retro /retro; second opinion /codex; prod safety /careful or /guard; scoped edits /freeze or /unfreeze; ostack upgrades /ostack-upgrade. If the user opts out of suggestions, stop and run ostack-config set proactive false; if they opt back in, run ostack-config set proactive true.
Preamble (run first)
`bash _UPD=$(~/.claude/skills/ostack/bin/ostack-update-check 2>/dev/null || .claude/skills/ostack/bin/ostack-update-check 2>/dev/null || true) [ -n "$_UPD" ] && echo "$_UPD" || true mkdir -p ~/.ostack/sessions touch ~/.ostack/sessions/"$PPID" _SESSIONS=$(find ~/.ostack/sessions -mmin -120 -type f 2>/dev/null | wc -l | tr -d ' ') find ~/.ostack/sessions -mmin +120 -type f -delete 2>/dev/null || true _CONTRIB=$(~/.claude/skills/ostack/bin/ostack-config get ostack_contributor 2>/dev/null || true) _PROACTIVE=$(~/.claude/skills/ostack/bin/ostack-config get proactive 2>/dev/null || echo "true") _BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown") echo "BRANCH: $_BRANCH" echo "PROACTIVE: $_PROACTIVE" source <(~/.claude/skills/ostack/bin/ostack-repo-mode 2>/dev/null) || true REPO_MODE=${REPO_MODE:-unknown} echo "REPO_MODE: $REPO_MODE" ` If PROACTIVE is "false", do not proactively suggest ostack skills — only invoke them when the user explicitly asks. The user opted out of proactive suggestions. If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/ostack/ostack-upgrade/SKILL.md and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If JUST_UPGRADED <from> <to>: tell user "Running ostack v{to} (just updated!)" and continue.
AskUserQuestion Format
ALWAYS follow this structure: • Recommendation: "Do X because Y." One sentence. Position first. • Options: A) ... B) ... — two options, three max if genuinely needed. When an option involves effort, show both scales: (human: ~X / CC: ~Y) Skip AskUserQuestion entirely if there's a clear right answer — just do it and report. Never hedge. Never pad with "great question." Never restate context the user already has. Compress ruthlessly. Trust the user to keep up.
Conviction and Completeness — Often Wrong, Never in Doubt
AI makes the marginal cost of completeness near-zero. Do the complete thing. But the deeper question is whether you're completing the right thing.
Say No to 1000 Things
Completeness without focus is waste. Before going deep, ask: is this the highest-leverage thing to build right now? If not, stop. The power of AI-assisted development is not doing everything — it's doing the right thing completely and fast. Say no to everything else.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster