executing-specs

Innei/ryugiProduct & project managementFrontend & design

executing-specs is a skill in Innei/ryugi, last changed 12 Nov 2026. It can run shell commands and reach the network — read the findings before installing.

From the author
Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or when they point you at a written design and ask you to build it in this session

At a glance

What it can touch

How much a skill can do, not whether it is risky.

Pattern check

1 item to review

Name copied from another skill

R38 · High · SKILL.md:2

Commit fe17c7b · 20 Nov 2026

How the check works

Pattern check:1 item to reviewSee it

QAI Index

44/QI

We rate every listed skill the same way, from 0 to 100.

A guide to compare by, not a verdict on the skill.

How it's scored

How the QAI Index is scored

Adoption · up to 40
GitHub stars on the repo that holds the skill, shared among its skills, and copies of the skill in other repos.
Quality · up to 30
Our pattern check, the format check, a named licence and a description of a sentence or more.
Upkeep · up to 20
How recently the skill's folder changed.
Trust · up to 10
An official collection, or an organisation that has confirmed its domain with GitHub.

Get an email when its check changes.

Keep it with the other skills you use, installed with one command.

Install

Sign in to see how to install it

Free with Google or an email link, no password needed. Then pick your agent and copy its steps.

Licence not identified
Licence
569
Repo stars
Publisher
Files
Logo
The project's logo, named in its Codex plugin manifest

What it can touch

Sign in to see the file and line behind each one

The summary at the top stays open to everyone. Signing in is free, with Google or an email link.

Pattern check

Pattern check: 1 item to review · commit fe17c7b · 20 Nov 2026

We checked every text file in this skill, at commit fe17c7b on 20 Nov 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

Format check

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 specFails

    The format our Agent Skills docs set out, held to the strictest version of each rule among the agents we check.

    • Error

      The name "executing-specs" doesn't match its folder "candidate". The spec requires them to match. N4

      Fix: Set name: candidate, or rename the folder to executing-specs.

    • 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: code-reviewer.md (200 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

      The name "executing-specs" doesn't match its folder "candidate". Claude Code shows the skill as /executing-specs, and the folder name also invokes it. N4

      Fix: Set name: candidate, or rename the folder to executing-specs.

    • Note

      Reference files over 100 lines with no table of contents at the top: code-reviewer.md (200 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

      The name "executing-specs" doesn't match its folder "candidate". claude.ai refuses an upload whose folder name doesn't match the skill name. N4

      Fix: Set name: candidate, or rename the folder to executing-specs.

    • Note

      Reference files over 100 lines with no table of contents at the top: code-reviewer.md (200 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

      The name "executing-specs" doesn't match its folder "candidate". OpenAI's own upload example uses a differently named folder, but the spec it follows says they must match. N4

      Fix: Set name: candidate, or rename the folder to executing-specs.

  • VS Code & CopilotPasses with warnings

    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.

    • Warning

      The name "executing-specs" doesn't match its folder "candidate". VS Code uses the folder name, candidate, instead. N4

      Fix: Set name: candidate, or rename the folder to executing-specs.

SKILL.md

We only show SKILL.md text here when its licence clearly allows it.

Read SKILL.md on GitHub (opens in a new tab)

Files

Changelog

Newest first: each commit that changed its folder on GitHub, and each change to its listing here.

  1. Listed on QAI
  2. Updated: docs(skills): executing-specs loads 7 KB lighter, with landing and ex… (e34ce62 (opens in a new tab))

Copies

These share its SKILL.md or its name and description but not all its files, so we list them separately.

QAI Index badge

Show this skill's QAI Index in a README or on a website. It links back to this page and changes when we refresh the catalog.

Preview of the QAI Index badge
[![QAI Index](https://qai.io/badge/skills/innei/ryugi/candidate--skills-2.svg)](https://qai.io/skills/innei/ryugi/candidate--skills-2)

More from Innei/ryugi

SkillQAI IndexWhat it can touchPattern checkLicenceUpdated
59/QI
  • Touches credentials
  • Runs shell commands
  • +2 more
Pattern check: Nothing flaggedNo licence20 Nov 2026
44/QI
  • Runs shell commands
  • Reaches the network
  • +1 more
Pattern check: 1 item to reviewNo licence12 Nov 2026
44/QI
  • Runs shell commands
Pattern check: 1 item to reviewNo licence13 Nov 2026
44/QI
  • Runs shell commands
  • Reaches the network
  • +1 more
Pattern check: 1 item to reviewNo licence12 Nov 2026
44/QI
  • Runs shell commands
Pattern check: 1 item to reviewNo licence13 Nov 2026
44/QI
  • Runs shell commands
Pattern check: 1 item to reviewNo licence12 Nov 2026
All skills in Innei/ryugi

Other Product & project management skills

Same category, most repo stars first.

SkillQAI IndexWhat it can touchPattern checkLicenceUpdated
74/QI
  • Runs shell commands
  • Bundles scripts
Pattern check: Nothing flaggedMIT3 Nov 2026
writing-plansUse when you have a spec or requirements for a multi-step task, before touching code

obra/superpowers

76/QI
  • Instructions only

Pattern check: Nothing flaggedMITUpdated 25 Sept 2026

76/QI
  • Instructions only
Pattern check: Nothing flaggedMIT25 Sept 2026
76/QI
  • Changes agent settings
  • Runs shell commands
  • +1 more
Pattern check: Nothing flaggedMIT1 Oct 2026
77/QI
  • Runs shell commands
Pattern check: Nothing flaggedMIT10 Oct 2026
discernment-nudgeAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

anthropics/skills

84/QI
  • Names web addresses

Pattern check: Nothing flaggedApache 2.0Updated 17 Aug 2026

84/QI
  • Names web addresses
Pattern check: Nothing flaggedApache 2.017 Aug 2026
70/QI
  • Touches credentials
  • Runs shell commands
  • +2 more
Pattern check: 3 items to reviewMIT20 Nov 2026

Repo facts from GitHub on 20 Nov 2026. Files read at commit fe17c7b.

QAI did not write these skills and is not affiliated with their authors unless a page says so. Logos and icons belong to their owners and are not a mark of approval. How we check