Agent skill

Recipe Quality Profile

by shinpr in shinpr/claude-code-workflows

Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml.

MITAuto-check passedDevelopment

Install Recipe Quality Profile

skills CLI
$ npx skills add shinpr/claude-code-workflows --skill recipe-quality-profile -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shinpr/claude-code-workflows recipe-quality-profile --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shinpr/claude-code-workflows.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/recipe-quality-profile .claude/skills/recipe-quality-profile && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
recipe-quality-profile
GitHub stars
694
Token cost
~1.1k tokens
SKILL.md length
493 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml.

  • Works in 6 steps: Use the current working repository as… → Build candidates from acceptance… → For each candidate, inspect supporting… → …
  • Asked to create
  • SKILL.md covers Purpose, Profile Contract, Authoring Flow and Result, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Recipe Quality Profile is an agent skill from shinpr/claude-code-workflows. Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Development workflows for Claude Code that keep broad exploration focused on the outcome you approved. The licence is MIT.

When your agent uses it

  • Asked to create
  • Update a repository quality profile

Example prompts

  • “Use the recipe-quality-profile skill to propose repository-specific quality policy for implementation and review and, after confirmation, creates or…”
  • “/recipe-quality-profile”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Use the current working repository as the target and read its docs/project-context/quality.yaml when present. For an existing profile, use…
  2. Build candidates from acceptance conditions expressed or enforced by repository instructions, contributor documentation, CI, manifests and…
  3. For each candidate, inspect supporting and contradicting evidence wherever it can change the candidate's applicability, accepted state, or…
  4. Retain a candidate only when failing its pass condition would change implementation acceptance and every repository fact it depends on has…
  5. Present proposed additions, changes, and removals, confirm that other dimensions remain unchanged, show the supporting and contradicting…
  6. Write only the confirmed profile content. Read the result and verify version 1, unique IDs, all required fields, observable conditions…

What it can do on your machine

Read from SKILL.md and the folder at commit a4ecd62. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Recipe Quality Profile loads about 1.1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shinpr/claude-code-workflows at commit a4ecd62, republished under its MIT licence (© shinpr). 493 words, ~1,112 tokens.

Download SKILL.mdSave it as .claude/skills/recipe-quality-profile/SKILL.md (or your agent's skills folder).
name
recipe-quality-profile
description
Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.
disable-model-invocation
true

Execute Skill: llm-friendly-context before proposing profile conditions or writing the profile. Execute Skill: coding-principles to distinguish repository-owned policy from general code-quality knowledge.

Purpose

Establish repository-specific implementation and code-review acceptance conditions with the user, then create or update docs/project-context/quality.yaml.

Requested policy change: $ARGUMENTS

Profile Contract

yaml
version: 1
review_dimensions:
  - id: stable-kebab-case-id
    applies_when: Observable condition that makes this repository rule relevant to a change.
    pass: Observable accepted state to verify.
    evidence:
      - "repository/path: section, identifier, or contract"

Each dimension owns one repository-specific quality decision. applies_when limits its implementation and review surface, pass defines the accepted state, and evidence identifies why the repository owns the rule.

Authoring Flow

  1. Use the current working repository as the target and read its docs/project-context/quality.yaml when present. For an existing profile, use the requested policy change as the update boundary; when none is supplied, ask for it and keep the profile unchanged.
  2. Build candidates from acceptance conditions expressed or enforced by repository instructions, contributor documentation, CI, manifests and scripts, schemas and public contracts, tests, or representative implementation patterns. For an update, derive candidates only from the requested policy change and preserve unrelated dimensions.
  3. For each candidate, inspect supporting and contradicting evidence wherever it can change the candidate's applicability, accepted state, or repository ownership. Separate observed repository facts from policy choices that require user confirmation.
  4. Retain a candidate only when failing its pass condition would change implementation acceptance and every repository fact it depends on has cited evidence. Give it the narrowest useful applies_when, one positive observable pass condition, and consolidate candidates that would produce the same finding and correction. Omit a candidate when required repository evidence is unavailable and report the exact evidence needed.
  5. Present proposed additions, changes, and removals, confirm that other dimensions remain unchanged, show the supporting and contradicting evidence, and state unresolved policy choices with their effect on implementation and review acceptance. Obtain explicit user confirmation of a proposal with no unresolved choices before writing.
  6. Write only the confirmed profile content. Read the result and verify version 1, unique IDs, all required fields, observable conditions, readable evidence references, and consistency with the confirmed proposal.

When no repository-specific dimension remains and no profile exists, report that repository evidence supports no profile content and leave the repository unchanged.

Show full SKILL.md (147 more words)Show less

Result

Before confirmation, report:

  • proposed additions, changes, and removals, plus the unchanged remainder;
  • supporting and contradicting evidence for each modification;
  • omitted candidates and the exact missing evidence;
  • policy choices requiring the user's decision and their effect on implementation and review acceptance.

After confirmation, report:

  • the profile path and whether it was created, updated, or left unchanged;
  • dimensions added, changed, or removed;
  • evidence used for each changed dimension;
  • an exact validation limitation when the result could not be verified.

Completion Check

  • Every retained dimension changes an implementation or review decision and cites repository or user-confirmed policy evidence
  • Conditions are positive, observable, and limited by applies_when
  • The profile contains repository-specific acceptance conditions only
  • Supporting and contradicting evidence were compared where they could change the proposal
  • The user confirmed the complete proposal before the repository write
  • Dimensions outside the update boundary remain unchanged
  • The written profile satisfies the Profile Contract

© shinpr, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/recipe-quality-profile of shinpr/claude-code-workflows.

Open the folder on GitHubat commit a4ecd62

Compare with similar skills

Recipe Quality Profile next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Recipe Quality Profile compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Recipe Quality Profile this skillshinpr/claude-code-workflows694—~1.1kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from shinpr/claude-code-workflows

All 30 skills in this repo
  • Integration E2E Testing

    shinpr/claude-code-workflows

    Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.

    694 GitHub stars~3.5k tokensUpdated 9 days ago
    Auto-check passed
  • AI Development Guide

    shinpr/claude-code-workflows

    Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates.

    694 GitHub stars~3.9k tokensUpdated 9 days ago
    Auto-check passed
  • Frontend AI Guide

    shinpr/claude-code-workflows

    Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates.

    694 GitHub stars~3k tokensUpdated 9 days ago
    Auto-check passed
  • Implementation Approach

    shinpr/claude-code-workflows

    Implementation strategy selection framework. An agent skill from shinpr/claude-code-workflows.

    694 GitHub stars~2.6k tokensUpdated 9 days ago
    Auto-check passed
  • Subagents Orchestration Guide

    shinpr/claude-code-workflows

    Guides subagent coordination through implementation workflows.

    694 GitHub stars~9.3k tokensUpdated 9 days ago
    Auto-check passed
  • Coding Principles

    shinpr/claude-code-workflows

    Language-agnostic coding principles for maintainability, readability, and quality.

    694 GitHub stars~2.4k tokensUpdated 9 days ago
    Auto-check passed

Categories

Questions about Recipe Quality Profile

What does Recipe Quality Profile do?

Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Recipe Quality Profile is an agent skill from shinpr/claude-code-workflows.yaml.

When should I use Recipe Quality Profile?

Recipe Quality Profile fits situations like: asked to create; update a repository quality profile.

How do I install Recipe Quality Profile in Claude Code?

Run `npx skills add shinpr/claude-code-workflows --skill recipe-quality-profile -a claude-code`. Or copy the skill folder (skills/recipe-quality-profile in shinpr/claude-code-workflows) into .claude/skills/recipe-quality-profile in your project. Claude Code loads it when a task matches its description.

How do I install Recipe Quality Profile in Codex?

Run `npx skills add shinpr/claude-code-workflows --skill recipe-quality-profile -a codex`. Or copy the skill folder (skills/recipe-quality-profile in shinpr/claude-code-workflows) into .agents/skills/recipe-quality-profile in your project. Codex loads it when a task matches its description.

Can I use Recipe Quality Profile in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shinpr/claude-code-workflows --skill recipe-quality-profile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recipe-quality-profile, .gemini/skills/recipe-quality-profile, .github/skills/recipe-quality-profile and .opencode/skills/recipe-quality-profile in your project.

What does Recipe Quality Profile need to run?

SKILL.md names no scripts, command-line tools or credentials: Recipe Quality Profile is instructions for the agent only.

Does Recipe Quality Profile access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Recipe Quality Profile safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Recipe Quality Profile use?

Recipe Quality Profile is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Recipe Quality Profile use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Recipe Quality Profile?

Skills that share tags, products or a category with Recipe Quality Profile: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Recipe Quality Profile?

shinpr (a GitHub user) maintains it in shinpr/claude-code-workflows, which has 694 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 1, 2026.

Source: shinpr/claude-code-workflows on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.