How do I install the Gstack skill?

Run npx skillmds@latest add onfire7777/gstack in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gstack safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gstack?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gstack free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gstack?

onfire7777 (@onfire7777) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gstack by onfire7777 — Agent Skill

Name: Gstack
Author: onfire7777

Gstack

Use when the user explicitly asks for gstack, Garry Tan's AI engineering stack, gstack methodology skills, gstack browser/PDF tooling, gstack office hours, gstack review, gstack QA, gstack ship, gstack security review, or gstack integration with Claude Code, Codex, OpenCode, Hermes, OpenClaw, Kiro, Cursor, or GBrain.

onfire7777 fce02d5 2.8 KB Updated Sep 17, 2026

File contents

GStack Universal Adapter

Canonical upstream checkout: %USERPROFILE%\.gstack\gstack

Use this as the compact entrypoint for Garry Tan's gstack without copying all generated host skills into every AI root. The full upstream skills remain in the gstack checkout and are loaded on demand through skill-router.

Load The Right GStack Skill

Use namespaced gstack skills to avoid collisions with generic names such as review, qa, ship, or browse:

skill-router skill gstack-office-hours
skill-router skill gstack-autoplan
skill-router skill gstack-plan-ceo-review
skill-router skill gstack-plan-eng-review
skill-router skill gstack-plan-design-review
skill-router skill gstack-review
skill-router skill gstack-qa
skill-router skill gstack-ship
skill-router skill gstack-cso
skill-router skill gstack-investigate
skill-router skill gstack-browse
skill-router skill gstack-make-pdf

Search when unsure:

skill-router skill search gstack
skill-router skill search "gstack security audit"
skill-router skill search "gstack browser"

Runtime Tools

The upstream build produces Windows executables in the canonical checkout:

%USERPROFILE%\.gstack\gstack\browse\dist\browse.exe
%USERPROFILE%\.gstack\gstack\browse\dist\find-browse.exe
%USERPROFILE%\.gstack\gstack\design\dist\design.exe
%USERPROFILE%\.gstack\gstack\make-pdf\dist\pdf.exe

Prefer the skill instructions before invoking a tool directly. The gstack skills contain the expected workflow, safety checks, and artifact conventions.

Integration Policy

Keep %USERPROFILE%\.gstack\gstack as the single upstream source checkout.
Keep generated gstack skill docs indexed read-only by the router.
Do not bulk-copy gstack skills into every agent root.
Use junctions or symlinks only where an upstream tool expects a fixed path.
For GBrain-aware coding workflows, prefer the generated GBrain host skills under %USERPROFILE%\.gstack\gstack\.gbrain\skills.
For OpenClaw-native conversational methods, use the upstream native skills under %USERPROFILE%\.gstack\gstack\openclaw\skills.

Maintenance

Update from the upstream repo, then regenerate/build:

skill-router gstack update
skill-router gstack build
skill-router gstack status

The router build wrapper follows the upstream README build flow but avoids the Windows shell-brace failure in the raw upstream bun run build script and restores generated source noise afterward.

---name: gstackdescription: Use when the user explicitly asks for gstack, Garry Tan's AI engineering stack, gstack methodology skills, gstack browser/PDF tooling, gstack office hours, gstack review, gstack QA, gstack ship, gstack security review, or gstack integration with Claude Code, Codex, OpenCode, Hermes, OpenClaw, Kiro, Cursor, or GBrain.---# GStack Universal AdapterCanonical upstream checkout: `%USERPROFILE%\.gstack\gstack`Use this as the compact entrypoint for Garry Tan's gstack without copying allgenerated host skills into every AI root. The full upstream skills remain in thegstack checkout and are loaded on demand through `skill-router`.## Load The Right GStack SkillUse namespaced gstack skills to avoid collisions with generic names such as`review`, `qa`, `ship`, or `browse`:- `skill-router skill gstack-office-hours`- `skill-router skill gstack-autoplan`- `skill-router skill gstack-plan-ceo-review`- `skill-router skill gstack-plan-eng-review`- `skill-router skill gstack-plan-design-review`- `skill-router skill gstack-review`- `skill-router skill gstack-qa`- `skill-router skill gstack-ship`- `skill-router skill gstack-cso`- `skill-router skill gstack-investigate`- `skill-router skill gstack-browse`- `skill-router skill gstack-make-pdf`Search when unsure:```bashskill-router skill search gstackskill-router skill search "gstack security audit"skill-router skill search "gstack browser"```## Runtime ToolsThe upstream build produces Windows executables in the canonical checkout:- `%USERPROFILE%\.gstack\gstack\browse\dist\browse.exe`- `%USERPROFILE%\.gstack\gstack\browse\dist\find-browse.exe`- `%USERPROFILE%\.gstack\gstack\design\dist\design.exe`- `%USERPROFILE%\.gstack\gstack\make-pdf\dist\pdf.exe`Prefer the skill instructions before invoking a tool directly. The gstack skillscontain the expected workflow, safety checks, and artifact conventions.## Integration Policy- Keep `%USERPROFILE%\.gstack\gstack` as the single upstream source checkout.- Keep generated gstack skill docs indexed read-only by the router.- Do not bulk-copy gstack skills into every agent root.- Use junctions or symlinks only where an upstream tool expects a fixed path.- For GBrain-aware coding workflows, prefer the generated GBrain host skills under `%USERPROFILE%\.gstack\gstack\.gbrain\skills`.- For OpenClaw-native conversational methods, use the upstream native skills under `%USERPROFILE%\.gstack\gstack\openclaw\skills`.## MaintenanceUpdate from the upstream repo, then regenerate/build:```bashskill-router gstack updateskill-router gstack buildskill-router gstack status```The router build wrapper follows the upstream README build flow but avoids theWindows shell-brace failure in the raw upstream `bun run build` script andrestores generated source noise afterward.

Frequently asked questions