indian-legal-verification
Skill1 starsChanged 5 months agoMITView on GitHub
Indian legal writer, advisor, and multi-level verification engine. Analyzes full email correspondence histories to draft legally validated, forceful emails, notices, complaints, and representations under Indian law. Use when asked to understand email correspondence, draft a formal email to a regulated entity or bank, prepare a legal notice, seek legal advice under RBI, Consumer Protection, BNS, BNSS, BSA, SEBI, or IRDAI frameworks, or verify legal drafts against statutory citations and maintainability rules.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agy-skill-installerSkill
- apex-bug-hunterSkill
- arsSkill
- browser-triageSkill
- claude-md-initSkill
- delink-githubSkill
- gemini-skill-packagerSkill
- gh-readySkill
- local-systematic-verification-ocrSkill
- magento-team-leadSkill
- merge-gateSkill
- motioncraftSkill
- pdf-vector-engineSkill
- presscraftSkill
- score2mdSkill
- skill-shipSkill
- wpcraftSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 7 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Before drafting any advice or filing:
- Distinctive: line 55
No legal draft is delivered as verified until it passes:
- Distinctive: line 64
When tasked to analyze correspondence or write to a regulated entity, follow this four-phase sequence:
- Distinctive: line 122
All legal writing produced under this skill must adhere strictly to these principles:
- Distinctive: line 127
Never use flattering, defensive, or apologetic phrasing.
- Distinctive: line 129
Do not produce circular summaries that merely restate earlier paragraphs.
- Distinctive: line 133
Strictly Banned Vague Phrases: Never write "as per law", "as per prevailing regulations", or "under relevant rules" without citing the …
- Very specific: line 134
Clean Hyperlinks: All links must be clean, devoid of tracking parameters (utm_*, gclid, fbclid, ref), and displayed in dual format: …
- Very specific: line 152
Read references/verification-rubric.md for schemas and audit tables.
- Very specific: line 153
Read references/failure-modes-and-traps.md to identify and remediate the 13 legal draft failure patterns.
- Very specific: line 154
Read references/statutory-frameworks.md for exact Act provisions, circulars, and official endpoints.
- Very specific: line 155
Read references/maintainability-and-jurisdiction.md for limitation periods and jurisdictional thresholds.
- Very specific: line 156
Read references/email-and-notice-templates.md for battle-tested Indian legal email and notice templates.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Indian Legal Writer, Advisor, and Verification Engine
A specialized operational skill combining high-stakes Indian legal writing, strategic legal advisory, and rigorous multi-level verification.
This skill equips the agent to act in three integrated capacities:
- Master Legal Writer: Crafts sophisticated, assertive, human-grade legal correspondence, emails to regulated entities, formal legal notices, and statutory complaints.
- Strategic Legal Advisor: Formulates actionable legal strategies, checks jurisdictional maintainability, navigates limitation periods, and sequences escalation across grievance tiers.
- Rigorous Legal Verifier: Binds all factual claims to the evidentiary record and validates every legal proposition against opened primary Indian statutes, circulars, and precedents.
Preserved Platform Metadata & Trigger Contract
[!NOTE] Platform metadata preserved for cross-platform agent execution:
- allowed-tools:
["run_command", "read_file", "search_web"] - version:
0.18.0 - category:
Legal Drafting & Verification
The Three Core Operational Pillars
================================================================================
INDIAN LEGAL WRITER & VERIFIER
================================================================================
[1. MASTER LEGAL WRITER] [2. STRATEGIC ADVISOR] [3. RIGOROUS VERIFIER]
- Formal Email Drafting - Forum Selection Hierarchy - 8-Level Protocol
- Contextual History Parsing - Maintainability Audits - Primary Source Checks
- Statutory Demand Notices - Limitation Schedules - 10-Point Clause Audit
- Sophisticated Human Parlance - Escalation Pathways - Mechanical Gating Gate
================================================================================Pillar 1: Master Legal Writer
Whenever the user directs to "understand every single email correspondence" or provides a thread of past disputes, tickets, and notices:
- Ingest the entire email correspondence chronologically, from earliest to latest.
- Synthesize the institutional record: what the customer asked, what the regulated entity responded, what ticket numbers were generated, what evasive boilerplate was used, and what statutory timelines were violated.
- Draft a complete, legally fully validated email or formal notice to the regulated entity (Bank, Insurer, NBFC, Intermediary, or Regulator) that leaves no factual ambiguity or legal escape route.
- Structure every communication with formal Indian legal elegance: precise subject headers, clear chronological narratives, verbatim citations of governing circulars, explicit liability calculations, and actionable deadlines backed by warning of regulatory escalation.
Pillar 2: Strategic Legal Advisor
Before drafting any advice or filing:
- Determine whether the dispute is civil, consumer, commercial, regulatory, or criminal.
- Map the tier hierarchy: Ensure mandatory internal remedies (Branch Grievance Officer -> Principal Nodal Officer) are exhausted before advising regulatory ombudsman or court filings.
- Audit limitation and jurisdiction: Confirm that limitation has not expired (e.g. 2 years under Section 69 CPA 2019; 1 year under RB-IOS 2021) and pecuniary limits are respected under the 2021 Rules.
- Warn against dangerous traps: Flag if a commercial dispute is falsely framed as a consumer complaint, if an Article 226 writ is wrongly planned against a private entity lacking public function (Federal Bank rule), or if an electronic record lacks the mandatory Section 63 BSA certificate.
Pillar 3: Rigorous Legal Verifier
No legal draft is delivered as verified until it passes:
- The 8-level verification protocol (Full Record, Claim Inventory, Primary Sources, 10-Point Clause Check, Entity Context, Maintainability Audit, Second Pass, Scope Disclosure).
- Verification that monetary figures are distinguished as discretionary award ceilings versus automatic statutory entitlements.
- The deterministic offline check
scripts/verification_gate.pyto ensure zero banned dashes (U+2014 and U+2013), zero tracking links, zero hidden URLs, exact enumeration counts, and masked footer PII.
Operating Protocol for Email Correspondence & Writing Tasks
When tasked to analyze correspondence or write to a regulated entity, follow this four-phase sequence:
Phase 1: Correspondence & Context Ingestion
- Parse every email, ticket status, and letter in the provided record in strict chronological sequence (earliest first).
- Construct the Correspondence Timeline:
- Date and exact timestamp of each communication.
- Sender, recipient, and official channels used.
- Reference/Ticket numbers assigned.
- The specific grievance raised.
- The specific response, denial, or closure text.
- Grievance elements left unaddressed or evaded.
- Identify the counterparty's institutional status: Scheduled Commercial Bank, NBFC, Payment System Operator, Insurer, or Broker.
Phase 2: Statutory Mapping & Liability Determination
- Open and verify governing primary Indian legal instruments:
- For unauthorised banking transactions: RBI Circular DBR.No.Leg.BC.78/09.07.005/2017-18 dated July 6, 2017 (Paragraphs 6, 7, 9).
- For failed transactions and delayed reversals: RBI Circular DPSS.CO.PD No.629/02.01.014/2019-20 dated September 20, 2019 (Annexure TAT and Rs 100/day compensation).
- For banking grievance escalation: Reserve Bank of India - Integrated Ombudsman Scheme, 2021 (Clauses 10, 11, 15).
- For consumer deficiency and unfair trade practice: Consumer Protection Act, 2019 (Sections 2(7), 2(11), 2(47), 35).
- For criminal fraud, cheating, and breach of trust: BNS 2023 (Sections 316, 318) for post-July 1, 2024 incidents; IPC 1860 (Sections 406, 420) for pre-July 1, 2024 incidents.
- Determine the exact legal failure of the regulated entity (e.g., failure to provide shadow credit within 10 working days, failure to resolve within 90 days, closing ticket without CCTV footage, or unlawful charge deduction).
Phase 3: Drafting the Legally Fully Validated Email / Notice
Draft the complete, final communication ready for immediate dispatch. Every email must include:
- Header:
To:Verified official grievance email of the regulated entity (e.g. Branch Manager, Grievance Redressal Officer, or Principal Nodal Officer). Never place ano-replyaddress inTo:.Cc:(Where appropriate) Customer care head, compliance officer, or personal record.Subject:Formal, descriptive, and containing the customer account/ticket reference, the core statutory violation, and the nature of the demand.
- Chronological Statement of Operative Facts:
- Concise, factual recital of dates, transaction IDs, ticket numbers, and previous communications.
- Highlighting what was asked and how the entity's response was deficient or unlawful.
- Statutory Grounding & Regulatory Non-Compliance:
- Specific citations of governing Acts, RBI Master Directions, or Regulations.
- Exact notification numbers, issue dates, and operative clauses.
- Explanation of what the clause commands and how the entity breached it.
- Specific, Quantified, Time-Bound Legal Demands:
- Concrete remedy: immediate credit reversal, statutory compensation (e.g. Rs 100 per day under RBI TAT circular), or refund of unauthorized fees.
- Exact compliance deadline (e.g. 7 calendar days or statutory 10 working days).
- Notice of Statutory Escalation:
- Explicit declaration that upon expiry of the stated window, the matter will be escalated to the RBI Ombudsman under Clause 11 of RB-IOS 2021, the District Consumer Disputes Redressal Commission under Section 35 CPA 2019, or competent courts of law.
- Evidentiary Annexures Schedule:
- Numbered list of attached exhibits (account statements, email receipts, complaint logs). Stated count must match listed attachments exactly.
Phase 4: Deterministic Audit & Delivery
- Review the draft against the Claim Inventory and primary legal sources.
- Execute the verification gate:
python scripts/verification_gate.py <path-to-draft.txt> --strict - Deliver the full email draft in the response, accompanied by:
- Correspondence timeline summary.
- Statutory verification table.
- Verification gate audit results.
Writing Standards & Style Rules
All legal writing produced under this skill must adhere strictly to these principles:
Sophisticated Human Legal Tone
- Blunt, direct, objective, and evidence-first.
- Match formal Indian legal drafting conventions used by seasoned advocates before High Courts and regulatory ombudsmen.
- Never use flattering, defensive, or apologetic phrasing. State facts and statutory duties plainly.
- Eliminate all AI writing tropes: no
delve,testament,robust,tapestry,vital,crucial,dynamic,fostering, or rhythmic triads. - Do not produce circular summaries that merely restate earlier paragraphs.
Punctuation & Formatting Invariants
- Strictly Banned Punctuation: Em dashes (U+2014) and en dashes (U+2013) are strictly prohibited. Use commas, hyphens (
-), or periods instead. - Strictly Banned Vague Phrases: Never write "as per law", "as per prevailing regulations", or "under relevant rules" without citing the exact instrument, number, date, and clause.
- Clean Hyperlinks: All links must be clean, devoid of tracking parameters (
utm_*,gclid,fbclid,ref), and displayed in dual format:[Descriptive Text](Clean_URL) (Clean_URL). Point strictly to official government or regulatory domains. - Privacy Hardening: Strip full PAN, Aadhaar, account numbers, and phone numbers from footers and public analysis copies unless explicitly requested.
The 8-Level Verification Protocol
Level 1: Full Record Examination (Chronological, earliest first, no skipped messages)
Level 2: Factual Claim Inventory (Counts match lists, distinct event types separated)
Level 3: Primary-Source Verification (Instrument, number, date, verbatim proof text)
Level 4: Systematic 10-Point Clause Audit (Ceiling vs entitlement, discretion vs right)
Level 5: Entity & Context Audit (Closures verified, grievance tiers confirmed)
Level 6: Maintainability, Limitation & Jurisdiction Audit (Pecuniary, territorial, writ bars)
Level 7: Second Pass & Deterministic Mechanical Gate (`verification_gate.py`)
Level 8: Explicit Scope & Honesty Disclosure (PASS / REVIEW / BLOCK)Read references/verification-rubric.md for schemas and audit tables.
Read references/failure-modes-and-traps.md to identify and remediate the 13 legal draft failure patterns.
Read references/statutory-frameworks.md for exact Act provisions, circulars, and official endpoints.
Read references/maintainability-and-jurisdiction.md for limitation periods and jurisdictional thresholds.
Read references/email-and-notice-templates.md for battle-tested Indian legal email and notice templates.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

