write-skill

Each tab says whether it installs commit 6f27f0c, the one we checked, or the latest version.

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  mkdir -p .claude/skills &&
  mkdir .claude/skills/write-skill &&
  cp -R "$tmp"/write-skill/. .claude/skills/write-skill/ &&
  rm -rf "$tmp"

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  out="$(mktemp -d)" &&
  cp -R "$tmp"/write-skill "$out"/write-skill &&
  (cd "$out" && zip -qr - write-skill) > write-skill.zip &&
  rm -rf "$tmp" "$out"

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  mkdir -p .agents/skills &&
  mkdir .agents/skills/write-skill &&
  cp -R "$tmp"/write-skill/. .agents/skills/write-skill/ &&
  rm -rf "$tmp"

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  mkdir -p .cursor/skills &&
  mkdir .cursor/skills/write-skill &&
  cp -R "$tmp"/write-skill/. .cursor/skills/write-skill/ &&
  rm -rf "$tmp"

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  mkdir -p .github/skills &&
  mkdir .github/skills/write-skill &&
  cp -R "$tmp"/write-skill/. .github/skills/write-skill/ &&
  rm -rf "$tmp"

gh skill install garrytan/gstack write-skill/SKILL.md@6f27f0c269cb33ad60b300ec10df63c2b9f296ba --agent github-copilot --scope project

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  mkdir -p .gemini/skills &&
  mkdir .gemini/skills/write-skill &&
  cp -R "$tmp"/write-skill/. .gemini/skills/write-skill/ &&
  rm -rf "$tmp"

gemini skills install https://github.com/garrytan/gstack.git --path write-skill --scope workspace

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/garrytan/gstack.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  git -C "$tmp" sparse-checkout set -- write-skill &&
  git -C "$tmp" checkout -q 6f27f0c269cb33ad60b300ec10df63c2b9f296ba &&
  mkdir -p .agents/skills &&
  mkdir .agents/skills/write-skill &&
  cp -R "$tmp"/write-skill/. .agents/skills/write-skill/ &&
  rm -rf "$tmp"

npx skills@1.7.4 add garrytan/gstack --skill write-skill

From the files and frontmatter at commit 6f27f0c. This is how much a skill can do, not whether it is risky.

What it can touch: Shell, network or credentials

• Runs shell commands

  Its instructions or files give the agent commands to run on your computer.

• Pre-approves tools

  Its allowed-tools field lists tools the agent may use without asking you first, in agents that honour it.

  SKILL.md:12

Pattern check: 1 item to review · commit 6f27f0c · 27 Oct 2026

• R34 · HighBroad tools pre-approved in allowed-tools

  SKILL.md:12 (opens in a new tab)

  - Bash

We checked every text file in this skill, at commit 6f27f0c on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

• Agent Skills specPasses with warnings

  The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

  • Warning

    Fields outside the spec: preamble-tier, version and triggers. Uploads to the Claude apps and API, and the spec's validator, reject the file; most agents ignore these fields. O1

    Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.

  • Warning

    allowed-tools is a list; the spec defines a space-separated string. gh skill publish rejects a list, though Claude Code accepts one. O5

    Fix: Write it on one line: allowed-tools: Bash Read Write Edit Grep Glob AskUserQuestion

  • Note

    The description doesn't say when to use the skill. D6

    Fix: Add a sentence such as "Use when …" naming the requests or files that should trigger it.

  • Note

    There is no license field, so readers can't tell whether they may reuse the skill. O2

    Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.

  • Note

    Reference files over 100 lines with no table of contents at the top: sections/preamble.md (256 lines). B5

    Fix: Add a short list of the sections at the top of each.

• Claude CodePasses

  Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

  • Note

    Claude Code ignores fields it doesn't know: preamble-tier, version and triggers. O1

    Fix: Check the spelling against Claude Code's field list, or delete them.

  • Note

    Reference files over 100 lines with no table of contents at the top: sections/preamble.md (256 lines). B5

    Fix: Add a short list of the sections at the top of each.

• Claude apps & API uploadFails

  Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

  • Error

    Upload and packaging fail on fields outside the spec: preamble-tier, version and triggers. O1

    Fix: Delete them, and keep your own data under metadata as text values.

  • Note

    allowed-tools is a list; the spec defines a space-separated string. O5

    Fix: Write it on one line: allowed-tools: Bash Read Write Edit Grep Glob AskUserQuestion

  • Note

    Reference files over 100 lines with no table of contents at the top: sections/preamble.md (256 lines). B5

    Fix: Add a short list of the sections at the top of each.

• OpenAI (Codex & API)Passes with warnings

  Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.

  • Warning

    Fields outside the spec: preamble-tier, version and triggers. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1

    Fix: Delete them, or move your own data under metadata as text values.

  • Note

    allowed-tools is a list; the spec defines a space-separated string. O5

    Fix: Write it on one line: allowed-tools: Bash Read Write Edit Grep Glob AskUserQuestion

• VS Code & CopilotPasses

  VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.

  • Note

    VS Code ignores fields it doesn't support: preamble-tier, version and triggers. O1

    Fix: Delete them unless another agent you target reads them.

  • Note

    allowed-tools is a list; the spec defines a space-separated string. O5

    Fix: Write it on one line: allowed-tools: Bash Read Write Edit Grep Glob AskUserQuestion

4 files