Grill with docs

Skill AravindS-Wick/aravindhan-skills/skills/grill-with-docs

148+ curated Claude AI skills — agent orchestration, security, multi-repo PRs, design, mobile & more. One-command install.

Install

npx -y skills add AravindS-Wick/aravindhan-skills --skill grill-with-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Forces grounding using live documentation (Redis, Postgres, external API docs, frameworks) fetched via curl or web search before generating integration code or database schemas.

SKILL.md

1.8 KB, 330 tokens by cl100k_base, as published. Nobody here has run it

Grounding with Live Docs Playbook

This skill instructs the agent to fetch external or official documentation from official websites or repositories before implementing database schemas, APIs, or libraries. This prevents using outdated schemas or hallucinating options/parameters.

Target Triggers

/grill-with-docs
"ground with latest schema"
"ground with docs"

Operational Steps

When executing tasks requiring database configuration, caching integration, or third-party APIs:

1. Identify Target APIs/Libraries

Determine the library versions or service endpoints (e.g., Redis, PostgreSQL, Prisma, Stripe, Firebase, AWS SDK, Next.js).
Pinpoint specific commands, functions, or schemas that need to be implemented.

2. Fetch Documentation Live

Do not rely entirely on internal model memory if there is ambiguity or a recent version change.
Use search_web to locate official guides or API docs.
Use read_url_content or read_browser_page to fetch and parse the target doc page.
Look specifically for syntax changes, deprecated options, error schemas, and configuration requirements.

3. Verify Database/Service Schema Compatibility

Check that fields, types, and constraints match exactly what the service/database expects.
Ground database queries against actual schemas defined in migration files, schemas (e.g., schema.prisma, SQL init files), or live database inspect outputs.

4. Implement Grounded Code

Write the schema, configuration, or API caller logic based on the extracted rules.
Document any specific assumptions or external links inside the codebase for developers.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.