mkadvise

Solid

Turn a raw idea into ONE honest recommendation: interview one question at a time until the problem, requirements, goals, non-goals, and constraints are CONFIRMED, then deliver a single verdict — do, don't, cheaper alternatives, trade-offs, ordered checklist, success metrics. Required: the user wants exactly ONE recommendation — not options, not a debate — and their framing is open to challenge (advise may answer a different question than the one asked). Triggers on "what should I do about X", "advise me on X", "am I approaching this right", "is this the right move". Do NOT use to be interrogated with no recommendation (→ mk:grill) — advise also interviews one question at a time, but only to reach a verdict. Do NOT use when the framing is settled and only the options are open (→ mk:brainstorming). Do NOT use to decide whether something is worth building (→ mk:office-hours). Do NOT use when you want several perspectives to argue it out (→ mk:party).

AI & Automation 15 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
40
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Advise One question at a time until the problem is confirmed, then one honest verdict. ## What This Is (and what it is not) Advise sits between interrogation and implementation. It **interviews** like `mk:grill`, but grill deliberately stops before recommending anything — advise exists to recommend. It **weighs options** like `mk:brainstorming`, but brainstorming enumerates alternatives for a problem you have already validated — advise starts before that, by questioning whether the problem is even the right one, and ends with a single pick rather than a menu. The whole value is the reframing. A user asking "should I use Redis or Memcached" often has a problem that needs neither. Answering the question as asked is the failure mode; the job is to find the real question first, confirm it with them, and only then answer. ## Route Fences | If the user wants… | Use | Not advise, because… | |---|---|---| | To be interrogated on their own plan, no answers given | `mk:grill` | Grill never recommends; advise exists to recommend | | Alternatives compared for a validated problem | `mk:brainstorming` | Advise questions the problem itself, and picks one option | | "Is this worth building at all?" | `mk:office-hours` | That is a product-existence question, upstream of advice | | Several perspectives to argue a trade-off | `mk:party` | Advise is one advisor giving one verdict | | A plan with phases | `mk:plan-creator` | Advice is not a plan; see Boundaries below | Overlap is the fai...

Details

Author
ngocsangyem
Repository
ngocsangyem/MeowKit
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

cf-advise

Decision advisory through a structured interview — never writes code or plans. Use when the user wants help DECIDING, not building — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "does it make sense to", "am I overthinking this", "what would you recommend", "is this a good idea", "pros and cons of". Interviews one question at a time to surface hidden requirements, then delivers a verdict-first recommendation with pitfalls and ranked alternatives. Unlike $cf-plan (writes an implementation plan / builds), this only advises. Unlike $cf-ask (looks up how existing code works), this reasons about a decision.

3 Updated today
dinhanhthi
AI & Automation Solid

mkgrill

Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).

15 Updated today
ngocsangyem
AI & Automation Solid

plastic-agent-advisor

Consult the advisor for expensive reasoning: one-way doors, plans, adversarial review of a plan or conclusion before an irreversible step, a deadlock after two failed attempts, or ranking several plausible options. Use when the user asks for a second opinion, a hard design decision, an architecture review, help breaking a deadlock, or says "ask the advisor". Also sets which advisor is the default when asked ("make Fable my advisor", "switch my advisor", "use the real advisor").

9 Updated 1 weeks ago
zalom