agentleFS
18studio18studio/simple_okf/.agents/skills/grillme/SKILL.md

grillme

Skill3 starsChanged 5 months agoMITView on GitHub

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Jekudy/grillme-skill★ 59same name
    2. MannyRodriguez-wk/workiva-SVC-skill-agent-library★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the questions in Russian, one at a time, waiting for feedback on each question before continuing.

    line 8
  2. Distinctive:

    If a question can be answered by exploring the codebase, explore the codebase instead.

    line 10
  3. Distinctive:

    Do not invent missing requirements, schema details, citations, source paths, or domain facts.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions in Russian, one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.

If a question can be answered by exploring the codebase, explore the codebase instead.

When the interview is complete and no blocking questions remain, switch to the okf skill workflow and record the user's answers as structured OKF documents. Follow all OKF rules from AGENTS.md and the okf skill workflow: inspect the existing bundle first, preserve stable concept IDs, create or update only evidence-backed concepts, use valid YAML frontmatter, prefer relative Markdown links, regenerate required indexes/graph outputs when concepts are added, removed, or renamed, and validate the bundle before finishing.

Do not invent missing requirements, schema details, citations, source paths, or domain facts. If the interview reveals unresolved gaps, write them explicitly as gaps or open questions in the OKF output rather than filling them in.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.