ask-dinesh

Routes a described situation to the right skills in the right order.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill ask-dinesh-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-dinesh
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/ask-dinesh
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill ask-dinesh-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a skill library grows large, knowing which skill fits a given situation — and in what order to run several — becomes the bottleneck. This router maps any described goal to the correct skill chain without doing the work itself. ## Core Features & Use Cases - Situation-to-skill routing: Describe a goal in plain language and receive an ordered chain of skills plus the always-on underlays (taste, critique, bias control) that load beneath them. - Live index verification: Reads SKILL-MAP.md and README.md at route time and confirms every skill against what exists on disk, so it never routes to a skill that was renamed or removed. - Fast path vs full path: One-skill asks get a single answer immediately; ambiguous or multi-stage asks get a gated routing interview and a full ordered chain with cuttable steps marked. - Use Case: You say "I need to redesign a booking flow before a client demo Friday" and receive the chain: frame the problem, check existing evidence, design the flow, build a throwaway prototype, then critique — with the new-study step cut for the deadline. ## Quick Start Ask which skill to use for your current task and describe the situation, stage, and deadline in one sentence.

Frequently Asked Questions about ask-dinesh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know which skill to use for a task?

Describe your situation — the object, the stage of work, and the stakes — and the router returns the matching skill or an ordered chain. It reads the live skill map and confirms each skill exists on disk before naming it.

How does a skill router decide between multiple skills?

It runs a routing gate that infers three facts: the object (screen, study, code, written piece), the stage (framing, researching, designing, building, reviewing), and the stakes (scrappy versus external-facing). It asks only the facts it cannot infer.

When should I not use a skill router?

Skip the router when the fit is obvious — a one-skill ask like writing a survey should load that skill directly. Routing a single-skill request through the full decision tree adds overhead with no benefit.

What happens if the router suggests a skill that does not exist?

It does not. The router verifies every candidate skill against the directory listing before naming it, and if a needed skill is genuinely unbuilt, it routes to the nearest real skill and points at the roadmap instead of inventing one.

Does the router do the actual work after routing?

No. It outputs the ordered skill chain, names the underlays that load beneath it, marks which steps are cuttable, and stops. Each routed skill owns its own method once named.