Update to Rohas Legal AI: Public

{
  "description": "Draft focused applications under India's Right to Information Act, 2005 for identifiable existing records held or controlled by the correct public authority. Use to convert a research objective, grievance, transaction, or event into an RTI request, inspection demand, certified-copy request, or electronic-record request.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 292
    }
  ],
  "name": "rti-application-drafter",
  "skill_md_contents": "---\nname: rti-application-drafter\ndescription: >-\n  Draft focused applications under India's Right to Information Act, 2005 for\n  identifiable existing records held or controlled by the correct public authority.\n  Use to convert a research objective, grievance, transaction, or event into an RTI\n  request, inspection demand, certified-copy request, or electronic-record request.\n---\n\n# India RTI Application Drafter\n\nAsk for records, not explanations or new analysis. Apply the current RTI Act and\nthe rules, fees, forms, portals, and language arrangements for the responsible\nCentral, State, legislative, judicial, or other competent authority.\n\n## Intake\n\nObtain the applicant's citizenship and contact details, objective, event and date\nrange, likely public authority and record custodian, known file or reference\nnumbers, desired record form, urgency, BPL status, submission route, and facts\nsupporting any life-or-liberty claim.\n\n## Drafting method\n\n1. Define the information outcome and research proactive disclosures, published\n   records, retention schedules, and the authority's subject allocation first.\n2. Identify the public authority that holds or controls each record. Distinguish\n   it from a body that merely regulates, funds, or may be able to obtain the record.\n3. Convert questions into narrow record descriptions using subject, creator or\n   recipient, record type, date range, file number, transaction, and custodian.\n   Request existing notes, orders, registers, correspondence, reports, contracts,\n   minutes, data extracts, or certified copies rather than reasons or opinions.\n4. Split unrelated record sets where that improves routing and search. Avoid vague\n   requests for \"all records,\" interrogatories, grievance argument, and accusations.\n5. Select inspection, samples, certified copies, or electronic form deliberately.\n   Specify accessible formats where needed without demanding creation of a new record.\n6. Anticipate Sections 8 and 9, third-party process under Section 11, severability\n   under Section 10, and exempt organisations under Section 24. Narrow personal,\n   fiduciary, commercial, security, copyright, and investigation-sensitive material;\n   state a supported public-interest case where legally relevant.\n7. Include transfer under Section 6(3) only as a fallback, the statutory response\n   route, applicable fee or BPL proof, and a substantiated life-or-liberty basis if used.\n8. Verify the current PIO, filing portal or address, payment method, word limit,\n   language, fee, and authority-specific Central or State rules on the filing date.\n\n## Output\n\nProvide a filing-ready application with numbered record requests, delivery form,\nfee or BPL statement, and applicant details, plus a routing note, source-to-request\nmap, exemption and narrowing notes, filing instructions, and deadline tracker.\n\n## Guardrails\n\nDo not invent file numbers or custodians, assert life or liberty without evidence,\nrequest the PIO to answer hypotheticals or create information, or include more\npersonal data than filing requires. Explain that RTI obtains records and is not a\nsubstitute for grievance redressal, discovery, or legal advice.\n"
}