New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Generate Manifest

by google in google/adk-recipes

Scan an ADK recipe directory and generate a manifest.yaml for it based on the schema at .github/schemas/manifest-schema.json.

OfficialApache-2.0Auto-check passed

Install Generate Manifest

skills CLI
$ npx skills add google/adk-recipes --skill generate-manifest -a claude-code

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

GitHub CLI
$ gh skill install google/adk-recipes generate-manifest --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/google/adk-recipes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/generate-manifest .claude/skills/generate-manifest && 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
generate-manifest
GitHub stars
10k
Token cost
~2.2k tokens
SKILL.md length
1,008 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Scan an ADK recipe directory and generate a manifest.yaml for it based on the schema at .github/schemas/manifest-schema.json.

  • Works in 7 steps: Identify the target recipe → Read the schema → Scan the recipe directory and infer only… → …
  • The user wants to create
  • Calls uv and make; reaches spdx.org
  • Generate a manifest.yaml for a recipe under core/

What it does

Generate Manifest is an agent skill from google/adk-recipes, published by the product's own GitHub organization. Scan an ADK recipe directory and generate a manifest.yaml for it based on the schema at .github/schemas/manifest-schema.json. Use when the user wants to create or generate a manifest.yaml for a recipe under core/, contrib/, or plugins/.

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

It works with GitHub. The repository describes itself as: A collection of agent recipes, reference patterns, and vertical plugins built with Agent Development Kit (ADK). The licence is Apache-2.0.

When your agent uses it

  • The user wants to create
  • Generate a manifest.yaml for a recipe under core/

Example prompts

  • “/generate-manifest”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Identify the target recipe
  2. Read the schema
  3. Scan the recipe directory and infer only what the code proves
  4. Make judgment calls explicitly
  5. Write the manifest
  6. Validate
  7. Report back

What it can do on your machine

Read from SKILL.md and the folder at commit c339821. 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

    Shell commands in SKILL.md call:

    • uv
    • make

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • spdx.org

    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

Generate Manifest loads about 2.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,008 words of instructions outside code blocks.

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

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 google/adk-recipes at commit c339821, republished under its Apache-2.0 licence (© google). 1,008 words, ~2,238 tokens.

Download SKILL.mdSave it as .claude/skills/generate-manifest/SKILL.md (or your agent's skills folder).
name
generate-manifest
description
Scan an ADK recipe directory and generate a manifest.yaml for it based on the schema at .github/schemas/manifest-schema.json. Use when the user wants to create or generate a manifest.yaml for a recipe under core/, contrib/, or plugins/.

Generate Manifest

Scan a recipe directory and produce a valid manifest.yaml for it, then validate it against the schema.

Process

1. Identify the target recipe

The user will provide a path to a recipe directory (e.g. core/python/rag-agent-search, contrib/python/my-recipe, plugins/retail/store-ops). If they don't, ask for it before proceeding.

2. Read the schema

Read .github/schemas/manifest-schema.json from the repo root to understand the current required and optional fields, allowed enum values, and constraints. Do not rely on memory — always read the live schema file so changes to it are automatically picked up.

3. Scan the recipe directory and infer only what the code proves

Read the following files if they exist:

  • pyproject.toml / requirements.txt — primary language (for language field)
  • app/agent.py or equivalent entry point — single vs multi-agent, agent count
  • Makefile — deploy targets (determines deployable)
  • app/ source files — stateful writes, datasource patterns
  • AGENTS.md — architecture notes if present

Field-by-field rules — read carefully before filling any field:

FieldRule
typeInfer from code. standalone = has its own runnable entry point: look for an if __name__ == "__main__" block, a make playground/run target, an adk web/adk run invocation, or a CLI. module = only importable (it just exports a root_agent/Agent for another workflow to orchestrate, with no way to run on its own). When ambiguous, re-read the schema's type description and prefer module only when there is genuinely no entry point.
deployableOPTIONAL. true only if a single make target or script deploys everything with no manual steps. Omit the field entirely if false (schema default is false).
largeOPTIONAL. Whether to opt into the relaxed size tier. Exact limits depend on whether the recipe lives under core/ or contrib/ or plugins/ and are defined in .github/policy.yml (recipe_size_limits) — as of writing: contrib/ and plugins/ default is 70 files / 2 MB and large is 200 files / 10 MB; core/ default is 500 files / 50 MB. Omit the field unless the recipe would otherwise exceed the default tier's limits (schema default is false).
statusAlways "active" unless there is explicit evidence of abandonment.
languageRead from file extensions or pyproject.toml. Never guess.
descriptionRead README.md and AGENTS.md only (author-written intent, not code). Write a draft of at most 15 words summarising what the recipe does. The schema requires at least 10 characters, so keep the draft comfortably above that. Append the comment # TODO: review and expand this draft description. If neither file exists or the intent is unclear, fall back to "DESCRIPTION" with the same TODO comment.
architecture.agentInfer from code only: count Agent( or equivalent constructor calls. single or multi. Omit the whole architecture block if uncertain.
architecture.statefulInfer from code: true only if the recipe writes persistently to an external system (DB, vector store, GCS) during normal operation — not just one-time setup.
architecture.datasourcesInfer from code: hardcoded = data literals in source; local = files bundled in repo; external = live systems queried at runtime. Can be multiple.
dependenciesInclude the block but comment it out entirely. Do NOT infer library or service names — GCP product names change and guesses will be wrong. Use the commented-out sample shown in the template.
ownership.teamAlways use the exact placeholder "TODO: Replace with your team name" — this is the literal string the validator checks for, so it correctly fails validation until a human fills it in. Never invent or infer a team name.
ownership.pocAlways use the exact placeholder "TODO: Replace with your GitHub user ID" — this is the literal string the validator checks for. Never invent or infer a GitHub ID from email addresses, file authors, or any other source.
ownership.contributorsOPTIONAL. Omit the field entirely. Leave a commented-out sample line so the author knows it exists. Never infer contributor IDs.
tagsInclude but comment out entirely, with a sample entry showing the expected style. Do NOT generate real tags — tag choices are the author's call.
licenseOPTIONAL. If the recipe's source tree contains a LICENSE file or the author has explicitly stated a license, record the SPDX identifier (e.g. "Apache-2.0", "MIT", "BSD-3-Clause"). Otherwise comment it out. Never infer or guess — only set it if it is explicitly declared.
Show full SKILL.md (334 more words)Show less
4. Make judgment calls explicitly

Before writing the manifest, briefly state what you found for each inferred field (type, deployable, architecture.*) and cite the specific file/line that supports your conclusion. This lets the user catch errors before they land in the file.

5. Write the manifest

Write manifest.yaml to the root of the recipe directory. Match the concise inline-comment style used by the existing manifests in core/ and contrib/ — allowed values shown as # Options: [...] after each field:

yaml
type: "..."          # Options: [standalone | module]
status: "active"     # Options: [active | inactive]
language: "..."      # Options: [python | java | go | kotlin | typescript]
description: "..."   # TODO: review and expand this draft description

# deployable: true   # (optional) one-command deploy, no manual steps; omit if false (default)
# large: true        # (optional) opt into the relaxed size tier; see .github/policy.yml (recipe_size_limits) for the exact numbers; omit if false (default)

architecture:          # (optional) omit the whole block if nothing below can be inferred from code
  agent: "..."          # Options: [single | multi]
  stateful: false       # Options: [true | false]
  datasources:          # Options: [hardcoded | local | external]
    - "..."

# dependencies: (optional) uncomment and fill in with canonical names
#   libraries:
#     - "ADK"
#     - "pandas"            # example — replace with actual libraries used
#   services:
#     - "GCP Project"
#     - "Cloud Run"         # example — replace with actual GCP/external services used

ownership:
  team: "TODO: Replace with your team name"
  poc: "TODO: Replace with your GitHub user ID"
  # contributors: (optional) uncomment and add GitHub IDs of additional contributors
  #   - "github-id-1"

# tags: (optional) uncomment and replace with meaningful labels
#   - "rag"               # example — use technology names, patterns, and use-case keywords
#   - "gemini"

# license: "Apache-2.0"  # (optional) SPDX identifier; only set if explicitly declared — see https://spdx.org/licenses/

Omit architecture entirely if none of its sub-fields can be determined from the code.

6. Validate

After writing the manifest, run the validator from the repo root (do not cd into tools/, and do not pass --active):

bash
uv run validate manifest <recipe-path>

<recipe-path> must be relative to the repo root (e.g. core/python/my-recipe, contrib/python/my-recipe, plugins/retail/store-ops), not an absolute path.

Interpret the result carefully — there are two kinds of failure:

  • Real schema errors (missing required field, invalid enum value, description under 10 characters, malformed YAML): fix these in the manifest and re-validate until they are gone.
  • ownership.team / ownership.poc placeholder errors: these are EXPECTED and must be left as-is. The validator deliberately fails while the placeholders are in place, to force a human to supply real values before merge. Do NOT invent a team name or GitHub ID to make validation pass.

So a correctly generated manifest will still report [FAIL] — but only on the two ownership placeholders, and nothing else. That is the intended outcome; report it to the user as "valid except for the ownership placeholders you need to fill in". Do not change or modify any other files in the repository. Also do not commit the changes.

7. Report back

Tell the user:

  1. What was inferred from the code and which file/line supports each inference.
  2. Which fields need human input before the manifest will pass validation: ownership.team and ownership.poc (placeholders — validation intentionally fails until these are replaced with real values). Also flag description (draft generated — must be reviewed and expanded) and dependencies/tags (commented out, ready to uncomment and fill in).

© google, Apache-2.0. 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 .agents/skills/generate-manifest of google/adk-recipes.

Open the folder on GitHubat commit c339821

Compare with similar skills

Generate Manifest 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.

Generate Manifest compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Generate Manifest this skillgoogle/adk-recipes10k—~2.2kAutomated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • 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

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-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

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.8k tokensUpdated today
    Research & ScienceAuto-check: notes

More from google/adk-recipes

All 14 skills in this repo

  • Retail Product Search Agent

    google/adk-recipes

    Official

    Builds a retail product search agent on Google Cloud, from catalog ingestion into BigQuery and Vector Search to ADK scaffolding, evaluation and Cloud Run deployment.

    10k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Align Recipe pyproject.toml

    google/adk-recipes

    Official

    Brings a Python recipe's pyproject.toml in line with the repo's CI rules, either as a read-only dry run or by rewriting the file while keeping comments.

    10k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Python Recipe Runnability Test Generator

    google/adk-recipes

    Official

    Generates a minimal tests/test_runnability.py for a Python agent recipe that imports the agent module and checks root_agent, adding only the mocks and env vars it needs.

    10k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Retail Virtual Try-On Agent

    google/adk-recipes

    Official

    Sets up a virtual try-on agent on Google Cloud that generates image and catwalk-video try-ons with Gemini, from first setup through local testing.

    10k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Scaffold Python ADK Recipe

    google/adk-recipes

    Official

    Creates a new Python recipe for the ADK recipes repository by running a scaffold script that copies template files, after confirming the output directory and recipe name.

    10k GitHub stars~931 tokensUpdated today
    Auto-check passed

  • GitHub Pull Request Reviewer

    google/adk-recipes

    Official

    Reviews a GitHub pull request and drafts a small set of inline comments in a human reviewing voice, each checkable from the line it points at, then posts them after approval.

    10k GitHub stars~8.4k tokensUpdated today
    Auto-check passed

Works with

Questions about Generate Manifest

What does Generate Manifest do?

Scan an ADK recipe directory and generate a manifest.yaml for it based on the schema at .github/schemas/manifest-schema.json. Generate Manifest is an agent skill from google/adk-recipes, published by the product's own GitHub organization.json.

When should I use Generate Manifest?

Generate Manifest fits situations like: the user wants to create; generate a manifest.yaml for a recipe under core/.

How do I install Generate Manifest in Claude Code?

Run `npx skills add google/adk-recipes --skill generate-manifest -a claude-code`. Or copy the skill folder (.agents/skills/generate-manifest in google/adk-recipes) into .claude/skills/generate-manifest in your project. Claude Code loads it when a task matches its description.

How do I install Generate Manifest in Codex?

Run `npx skills add google/adk-recipes --skill generate-manifest -a codex`. Or copy the skill folder (.agents/skills/generate-manifest in google/adk-recipes) into .agents/skills/generate-manifest in your project. Codex loads it when a task matches its description.

Can I use Generate Manifest 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 google/adk-recipes --skill generate-manifest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-manifest, .gemini/skills/generate-manifest, .github/skills/generate-manifest and .opencode/skills/generate-manifest in your project.

What does Generate Manifest need to run?

Going by SKILL.md and its folder, Generate Manifest needs the command-line tools its instructions call (uv and make). Our summary lists: Python 3.

Does Generate Manifest access the network?

SKILL.md names 1 domain. In commands or code: spdx.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Generate Manifest 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 Generate Manifest use?

Generate Manifest is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Generate Manifest use?

About 2.2k tokens (SKILL.md is roughly 9k 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 Generate Manifest?

Skills that share tags, products or a category with Generate Manifest: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Generate Manifest?

google (a GitHub organization, an official publisher) maintains it in google/adk-recipes, which has 10,421 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.

Source: google/adk-recipes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.