Inspiration
India has about 731 Krishi Vigyan Kendras (KVKs), the farm science centres that farmers phone or message about pests, fertiliser and scheme payments. The answer depends on who picks up. Vetted advice sits in PDFs and in experts' heads. A wrong answer about a pesticide can hurt someone.
Tab, an AI assistant, set out to build the help desk these centres need: fast for routine questions, and never careless with the dangerous ones.
What it does
- Triage. Every farmer query becomes a Jira Service Management ticket. An issue panel shows:
- the request type (Pest/Disease, Scheme, Market, Emergency);
- category, crop and urgency;
- the queue it belongs in;
- a draft reply. One click applies labels that JSM automation uses to route the ticket.
- Safety floor in code, before any AI.
- Words about swallowing ("drank", "pi liya", "जहर"), or symptoms after spraying ("headache and sweating"), make the ticket an Emergency. It gets a 15-minute callback SLA and first-aid steps only.
- Any of 50+ pesticide names, or a dose question, gets no drafted product or dose; an expert signs off.
- The Rovo agent can add escalations but can never remove one.
- Vetted answers only. 23 advisories so far: rice, tomato, cotton, chilli, onion, wheat, mango, sugarcane, banana pests and diseases, plus PM-KISAN, KCC, Soil Health Card, PMFBY and e-NAM.
- Each cites its source, mostly TNAU Agritech pages from Tamil Nadu Agricultural University.
- Ambiguous symptoms ("paddy leaves turning yellow") get a checklist to tell the possible causes apart, not a guess.
- No match goes to a human.
- Outbreak radar. Pest tickets are grouped by district from their labels, so a centre sees a cluster early.
- Safety test sheet. 50 adversarial queries, including Hindi and Hinglish poisoning reports and dose requests. All 50 pass. The sheet runs live on the demo page and in the repo's tests.
How we built it
- Forge (Node 22) modules:
- a
rovo:agentwith three actions: Triage farmer query, Look up vetted advice, Apply triage labels; - a
jira:issuePanelin UI Kit; - a resolver.
- a
- Jira access is through
@forge/api, using theread:jira-workandwrite:jira-workscopes. - One small core. Triage, the safety guard and retrieval are a single pure-JavaScript core that also runs the public demo, so the demo is the real logic.
- Setup guide.
JSM_SETUP.mdcovers request types, queues, SLAs and the automation rule.
Challenges we ran into
Hark's first review broke our safety claims:
- "My neighbour drank pesticide" got pest advice.
- "Son sprayed yesterday, headache and sweating" was rated low urgency.
We rebuilt the guard as rules that run first. Then we tested it on 50 adversarial queries. That surfaced a subtler bug: "ate" matched inside "glyphosate", which raised a false alarm. Matching on whole words fixed it.
Accomplishments that we're proud of
- A help desk that cannot be talked into giving a dose.
- Every sentence it drafts has a source.
What we learned
- Guardrails belong in code the AI cannot override.
- A visible test sheet earns more trust than a promise.
What's next for KrishiDesk
- Deploy to a Jira Service Management site with the advisories in Confluence (one page per advisory, each with an owner and a version).
- Replies in Hindi and Marathi.
- A WhatsApp intake channel.
- A pilot with one KVK.
Built with
atlassian-forge, rovo, jira-service-management, confluence, ui-kit, react, javascript, node.js
Access for judges (installation link)
The app is Forge, production v2.0.0, shared via the Atlassian developer console installation link (Install onto Jira and Confluence). After install, open any Jira issue to see the "KrishiDesk triage" issue panel, and open Rovo to chat with the "KrishiDesk Advisor" agent. Our own dev site (tabforakshay.atlassian.net, project KD) is not public, so the gallery shows its live screens: the issue panel on KD-1 and the Rovo agent answering on KD-1.
How it meets the technology requirement
KrishiDesk is a Forge app (manifest.yml in the repo): a rovo:agent with three actions, a jira:issuePanel module in UI Kit, a resolver, and Jira REST access through @forge/api with the read:jira-work and write:jira-work scopes. It integrates with Jira Service Management tickets, Jira issues and Rovo, and is deployed to production and installed in Jira and Confluence.
Category
Apps for Specialized Industries (agriculture and farm-advisory services). Also entered for Best Agents - Rovo/Assignable agents.
Try it out
- Install link (Forge, Jira + Confluence): see above
- Web demo of the same triage and safety core (no login): https://krishidesk.sites.tab.bot/
- Source (MIT licence, manifest.yml at the root): https://github.com/tab-for-akshay/krishidesk
- Privacy statement: https://github.com/tab-for-akshay/krishidesk/blob/main/PRIVACY.md
- Demo video: https://youtu.be/2p9_kt9rWBI
Team and AI disclosure
Built by Tab, an AI assistant, for team lead Akshay Wagh. Tab wrote the code; Akshay set the goal and reviews the entry. Team name: Tab x Akshay. The knowledge base cites public pages and is not a substitute for an expert's advice.
Built With
- atlassian-forge
- confluence
- javascript
- jira-service-management
- node.js
- react
- rovo
- ui-kit