recipe-schema-explore

recipe-schema-explore is a skill for Claude Code from fakoli/fakoli-plugins. It costs 25 tokens per session (435 once invoked), scanned A, original, MIT.

A Google Workspace API inspection workflow that shows available methods, their parameters, and the data types they use before you make a request.

In plain words
What is it for?
Use it to explore Gmail, Drive, Sheets, Calendar, or other Google Workspace APIs and prepare safe commands.
Why use it?
It reduces guesswork when using an unfamiliar Google API and lets you test a request without changing anything.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the gws plugin — 94 skills, 15 commands, 11 agents shipped together

Good fit Use it to explore Gmail, Drive, Sheets, Calendar, or other Google Workspace…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fakoli/fakoli-plugins/recipe-schema-explore
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fakoli/fakoli-plugins --skill recipe-schema-explore
Clone the repo
git clone --depth 1 https://github.com/fakoli/fakoli-plugins

Made for: Claude Code.

Or install gws, the plugin that ships this one along with the rest of its 94 skills, 15 commands, 11 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for recipe-schema-explore

README.md
[![agentmods](https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-schema-explore.svg)](https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-schema-explore)
Your own site
<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-schema-explore"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-schema-explore.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 435 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00435
Opus 5 $0.00013 $0.00217
Sonnet 5 $0.00005 $0.00087
Haiku 4.5 $0.00003 $0.00044

Measured 3d ago against content hash 349375a4d948, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

recipe-schema-explore scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/gws/skills/recipe-schema-explore/SKILL.md · 70 lines

What it actually says

Explore an API Before Using It

Discover and introspect any Google Workspace API using gws schema before executing commands.

When to Use

Use this workflow when the user wants to explore an unfamiliar API, check method parameters, or understand the request/response structure before making calls.

Steps

  1. List available methods for a service:

    gws <service> --help
    

    Example:

    gws drive --help
    gws sheets --help
    
  2. Drill into a resource:

    gws drive files --help
    gws sheets spreadsheets --help
    
  3. Inspect method parameters:

    gws schema drive.files.list
    gws schema calendar.events.insert
    
  4. Resolve nested type references:

    gws schema sheets.spreadsheets.create --resolve-refs
    
  5. Inspect a specific type:

    gws schema gmail.Message
    gws schema drive.File
    
  6. Test with a dry run:

    gws drive files list \
      --params '{"pageSize": 3}' \
      --fields "files(id,name)" \
      --dry-run
    
  7. Execute with confidence:

    gws drive files list \
      --params '{"pageSize": 3}' \
      --fields "files(id,name)"
    

Tips

  • Always start with gws schema when using an API for the first time
  • Use --resolve-refs to see the full schema without chasing $ref pointers
  • The schema data comes from Google's live Discovery Service — always current
  • Combine --help (for CLI flags) with gws schema (for API structure)
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 70 lines · 25 tokens per session scan A 349375a4d948

Subscribe to this mod's changes

recipe-schema-explore is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 435 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

explain

Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to…

Marcel-Bich/marcel-bich-claude-marketplace · 0 tokens

a-unslop-code

Finds what makes source code read as AI-written and points you at the parts that actually ship bugs. Sorts every tell into three buckets and fixes them in that order: bugs (swallowed errors, a made-up API, a left-in "rest of the code" stub), substance (tutorial-shaped boilerplate, over-engineering, code that ignores…

imisic/claude-marketplace · 187 tokens

zasilkovna

Integrate and manage Zásilkovna (Packeta) shipping for Czech and Slovak logistics. Create shipments, generate labels, track packages, manage pickup points, and configure webhooks using the Zásilkovna API. Covers both the REST API and SOAP API. Includes ready-to-run CLI scripts for all API operations. Context: User…

lukaskellerstein/claude-my-marketplace · 211 tokens

media-higgsfield-explainer

A Higgsfield workflow for making non-photorealistic narrated explainer videos. It pairs each narration line with a 10-second animated clip and joins the clips into one finished video.

modu-ai/moai-cowork · 236 tokens

career-junior-onboarding

A self-onboarding coach for new and junior employees during their first 90 days at a company. Onboarding means learning how the organization, people, tools, and work processes operate.

modu-ai/moai-cowork · 161 tokens

push-notifications

Generate push notification infrastructure with APNs registration, handling, and rich notifications. Use when adding push notifications, configuring APNs, notification categories/actions, or rich notifications with images and custom UI.

rshankras/claude-code-apple-skills · 42 tokens