DIGIT Platform
Gateway skill for the DIGIT eGov platform. Routes to specialized skills based on what the user needs.
Always start by identifying the user's intent, then route to the right skill.
Persona Detection
digraph persona_router {
rankdir=TB
node [shape=box style=rounded]
input [label="User message" shape=ellipse]
detect [shape=diamond label="What does the\nuser need?"]
setup [label="digit-tenant-setup\n(Skill tool)" style="filled" fillcolor="#cce5ff"]
pgr [label="digit-pgr-operations\n(Skill tool)" style="filled" fillcolor="#d4edda"]
ui [label="digit-ui-building\n(Skill tool)" style="filled" fillcolor="#fff3cd"]
input -> detect
detect -> setup [label="set up city\ncreate employee\nconfigure tenant"]
detect -> pgr [label="file complaint\nassign/resolve\ncheck status\nview summary"]
detect -> ui [label="build UI\ncreate frontend\nmodify screens"]
}
Routing Table
| Persona |
Trigger phrases |
Route to skill |
| Citizen |
"I want to complain", "check my complaint status" |
digit-pgr-operations |
| GRO |
"assign complaint", "pending grievances" |
digit-pgr-operations |
| LME |
"field worker", "assigned to me", "mark resolved" |
digit-pgr-operations |
| DGRO |
"department complaints", "sanitation issues" |
digit-pgr-operations |
| Viewer |
"how many pending", "complaint summary" |
digit-pgr-operations |
| Admin |
"set up city", "create employee", "onboard municipality" |
digit-tenant-setup |
| UI Builder |
"build UI", "create frontend", "PGR dashboard" |
digit-ui-building |
How to route: Invoke the target skill using the Skill tool. For example, if the user wants to file a complaint, call Skill(skill="digit-pgr-operations").
General Principles
These apply across ALL sub-skills:
- One question at a time. Never ask two things in one message.
- Never show raw JSON, IDs, or codes to non-technical users.
- Confirm before acting. Summarize what you'll do, then do it.
- If something fails: Retry once, then "Let me try a different approach."
- All DIGIT API calls through MCP tools only. Never use Bash/curl. The DIGIT APIs are not publicly exposed outside the MCP layer.
- Always call
configure first, then enable_tools for the required groups.
Environment
- Key:
chakshu-digit | URL: https://api.egov.theflywheel.in
- State tenant:
tenant | Default login: pg (ADMIN)
Sub-Skills Reference
| Skill |
Purpose |
Key patterns |
digit-tenant-setup |
Set up new cities, create employees, configure PGR |
Hard-gated 10-step procedure with verification gates |
digit-pgr-operations |
File, assign, resolve, rate complaints |
PGR state machine, persona-specific flows |
digit-ui-building |
Build PGR complaint management UIs |
SDK-first, phase-gated build process |
1---2name: digit3description: Use when working with DIGIT eGov platform, PGR complaints, tenant setup, or building complaint management UIs. Also activate for plain-English city setup requests or citizen complaint filing.4---56# DIGIT Platform78Gateway skill for the DIGIT eGov platform. Routes to specialized skills based on what the user needs.910**Always start by identifying the user's intent**, then route to the right skill.1112---1314## Persona Detection1516```dot17digraph persona_router {18 rankdir=TB19 node [shape=box style=rounded]2021 input [label="User message" shape=ellipse]22 detect [shape=diamond label="What does the\nuser need?"]2324 setup [label="digit-tenant-setup\n(Skill tool)" style="filled" fillcolor="#cce5ff"]25 pgr [label="digit-pgr-operations\n(Skill tool)" style="filled" fillcolor="#d4edda"]26 ui [label="digit-ui-building\n(Skill tool)" style="filled" fillcolor="#fff3cd"]2728 input -> detect29 detect -> setup [label="set up city\ncreate employee\nconfigure tenant"]30 detect -> pgr [label="file complaint\nassign/resolve\ncheck status\nview summary"]31 detect -> ui [label="build UI\ncreate frontend\nmodify screens"]32}33```3435## Routing Table3637| Persona | Trigger phrases | Route to skill |38|---------|----------------|----------------|39| Citizen | "I want to complain", "check my complaint status" | `digit-pgr-operations` |40| GRO | "assign complaint", "pending grievances" | `digit-pgr-operations` |41| LME | "field worker", "assigned to me", "mark resolved" | `digit-pgr-operations` |42| DGRO | "department complaints", "sanitation issues" | `digit-pgr-operations` |43| Viewer | "how many pending", "complaint summary" | `digit-pgr-operations` |44| Admin | "set up city", "create employee", "onboard municipality" | `digit-tenant-setup` |45| UI Builder | "build UI", "create frontend", "PGR dashboard" | `digit-ui-building` |4647**How to route**: Invoke the target skill using the `Skill` tool. For example, if the user wants to file a complaint, call `Skill(skill="digit-pgr-operations")`.4849---5051## General Principles5253These apply across ALL sub-skills:5455- **One question at a time.** Never ask two things in one message.56- **Never show raw JSON, IDs, or codes** to non-technical users.57- **Confirm before acting.** Summarize what you'll do, then do it.58- **If something fails**: Retry once, then "Let me try a different approach."59- **All DIGIT API calls through MCP tools only.** Never use Bash/curl. The DIGIT APIs are not publicly exposed outside the MCP layer.60- **Always call `configure` first**, then `enable_tools` for the required groups.6162---6364## Environment6566- **Key**: `chakshu-digit` | **URL**: `https://api.egov.theflywheel.in`67- **State tenant**: `tenant` | **Default login**: `pg` (ADMIN)6869---7071## Sub-Skills Reference7273| Skill | Purpose | Key patterns |74|-------|---------|-------------|75| `digit-tenant-setup` | Set up new cities, create employees, configure PGR | Hard-gated 10-step procedure with verification gates |76| `digit-pgr-operations` | File, assign, resolve, rate complaints | PGR state machine, persona-specific flows |77| `digit-ui-building` | Build PGR complaint management UIs | SDK-first, phase-gated build process |
chakshugautam