Claude Skills by praxstack

Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). (gstack)

Report-only QA testing. (gstack)

Systematically QA test a web application and fix bugs found. (gstack)

Weekly engineering retrospective. (gstack)

Pre-landing PR review. (gstack)

Pull data from a web page. (gstack)

Import cookies from your real Chromium browser into the headless browse session. (gstack)

Configure deployment settings for /land-and-deploy.

Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. (gstack)

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack)

Codify the most recent successful /scrape flow into a permanent browser-skill on disk. (gstack)

Turn vague intent into a precise, executable spec in five phases. (gstack)

Keep gbrain current with this repo's code and refresh agent search guidance in CLAUDE.md. (gstack)

Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)

Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.

Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Writing, exploit: shape raw material into an article, paragraph by paragraph.

A persistent, compounding knowledge base combining Karpathy's LLM Wiki pattern with a structured knowledge graph. Ingest documents once — the LLM writes wiki pages, extracts entities/relations into the graph, and stores raw content for evidence retrieval. Knowledge accumulates and cross-references; it is never re-derived from scratch.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.

Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

**You own the skill's voice.** Agent-facing prose has a higher bar than human prose; unhelpful sentences become instructions. 1. Use the **create-skill** skill (Cursor's built-in for authoring SKILL.md files). 2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve. 3. Test cases if structural; skip if subjective. 4. Run **Opening a PR**. When in doubt, delete; prose earns its keep by changing a decision. Tell it to do the thing and s...

Configure which models pstack uses per role. Detects your available models and writes an always-applied rule that overrides the skill defaults. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.

Build and operate Python Azure IoT Edge modules with robust messaging, deployment manifests, observability, and production readiness checks.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Generate a custom checklist for the current feature based on user requirements.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Create or update the project constitution from interactive or provided principle inputs.

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create or update the feature specification from a natural language feature description.

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Use this template for domain-specific security testing (cryptographic testing, web security methodologies, etc.).

Use this template for language-specific fuzzers (libFuzzer, AFL++, cargo-fuzz, etc.).

Use this template for cross-cutting techniques that apply to multiple tools (harness writing, coverage analysis, sanitizers, dictionaries, etc.).

Use this template for static analysis tools (Semgrep, CodeQL) and similar standalone CLI tools.

Update a markdown file section with an index/table of files from a specified folder.

Drive Markdown Viewer Pro (Vite + vanilla JS) like a user and capture proof. Use when verifying UI changes, markdown rendering, themes, view modes, or any feature in this repo's web app.

Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.