@jcode.labs/ragmir 2.0.0

package/skills/ragmir-audio-summary/xtts-voice.py

@@ -0,0 +1,46 @@
+#!/usr/bin/env python3
+"""Render a text file to WAV with Coqui XTTS-v2.
+
+Run with the dedicated venv interpreter:
+  ~/.local/share/voice-forge/xtts/bin/python xtts-voice.py <text.txt> <out.wav> [speaker]
+
+Env: XTTS_SPEAKER (preset name), XTTS_LANG (default "fr").
+"""
+import os
+import sys
+
+os.environ.setdefault("COQUI_TOS_AGREED", "1")
+
+
+def main() -> None:
+    if len(sys.argv) < 3:
+        sys.exit("usage: xtts-voice.py <text.txt> <out.wav> [speaker]")
+    text_file, out_wav = sys.argv[1], sys.argv[2]
+    speaker = sys.argv[3] if len(sys.argv) > 3 else os.environ.get("XTTS_SPEAKER", "Ana Florence")
+    language = os.environ.get("XTTS_LANG", "fr")
+
+    with open(text_file, encoding="utf-8") as handle:
+        text = handle.read().strip()
+    if not text:
+        sys.exit("error: empty text file")
+
+    from TTS.api import TTS
+
+    tts = TTS("tts_models/multilingual/multi-dataset/xtts_v2")
+    speakers = list(getattr(tts, "speakers", None) or [])
+    if speakers and speaker not in speakers:
+        sys.stderr.write(f"speaker '{speaker}' not found; falling back to '{speakers[0]}'\n")
+        speaker = speakers[0]
+
+    tts.tts_to_file(
+        text=text,
+        speaker=speaker,
+        language=language,
+        file_path=out_wav,
+        split_sentences=True,
+    )
+    print(out_wav)
+
+
+if __name__ == "__main__":
+    main()

package/skills/ragmir-legal-dossier/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: ragmir-legal-dossier
+description: >-
+  Prepare cited legal-dossier work products from a local Ragmir knowledge base. Use when the user asks
+  for a legal chronology, clause search, dossier summary, evidence table, redaction review, or
+  professional-review handoff grounded in confidential local documents.
+---
+
+# Ragmir Legal Dossier
+
+Use this skill for legal or quasi-legal dossiers where confidentiality, evidence separation, and
+professional review matter. This skill does not provide final legal advice. It prepares structured,
+cited work products for review by the user or a qualified professional.
+
+## Safety Rules
+
+- Treat source documents, retrieved passages, party names, dates, amounts, identifiers, and draft
+  outputs as confidential.
+- Keep generated work under `.ragmir/reports/` unless the user explicitly asks for a sanitized
+  tracked artifact.
+- Do not upload documents, snippets, queries, vector stores, or generated drafts to hosted services.
+- Do not present conclusions as legal advice. Separate evidence, inference, uncertainty, and review
+  items.
+- Prefer short cited summaries over long raw extracts.
+- Flag missing documents, unsupported files, stale indexes, and ambiguous source passages.
+
+## Recommended Redaction Patterns
+
+If a legal dossier includes professional secrecy, case identifiers, or French personal identifiers,
+add project-local redaction patterns in `.ragmir/config.json` before indexing. Keep patterns scoped to the
+dossier and test them on non-sensitive samples first.
+
+```json
+{
+  "redaction": {
+    "enabled": true,
+    "builtIn": true,
+    "patterns": [
+      {
+        "name": "case_reference",
+        "pattern": "\\b(?:RG|N°\\s*RG|No\\s*RG)\\s*[:\\-]?\\s*[0-9A-Z/\\-]{4,}\\b",
+        "replacement": "[CASE_REFERENCE]"
+      },
+      {
+        "name": "french_nir",
+        "pattern": "\\b[12]\\s?\\d{2}\\s?\\d{2}\\s?\\d{2}\\s?\\d{3}\\s?\\d{3}\\s?\\d{2}\\b",
+        "replacement": "[FRENCH_NIR]"
+      },
+      {
+        "name": "iban",
+        "pattern": "\\b[A-Z]{2}\\d{2}(?:\\s?[A-Z0-9]){11,30}\\b",
+        "replacement": "[IBAN]"
+      }
+    ]
+  }
+}
+```
+
+After changing redaction rules, rebuild the index:
+
+```bash
+pnpm exec ragmir ingest --rebuild
+pnpm exec ragmir security-audit --strict
+```
+
+## Retrieval Workflow
+
+Start from readiness checks:
+
+```bash
+pnpm exec ragmir doctor
+pnpm exec ragmir audit
+pnpm exec ragmir audit --unsupported
+pnpm exec ragmir security-audit --strict
+```
+
+Then run targeted retrieval passes:
+
+```bash
+pnpm exec ragmir search "parties obligations dates amounts" --top-k 8
+pnpm exec ragmir search "termination clause liability indemnity notice" --top-k 8
+pnpm exec ragmir search "timeline meeting decision approval refusal" --top-k 8
+pnpm exec ragmir ask "Which documents support the chronology of events?" --top-k 8
+```
+
+When MCP is available, prefer `ragmir_status`, `ragmir_search`, `ragmir_ask`, `ragmir_audit`, and
+`ragmir_security_audit` so the agent can keep retrieval bounded and cited.
+
+## Output Formats
+
+### Dossier Summary
+
+```markdown
+# Legal Dossier Summary
+
+## Scope
+
+## Evidence Inventory
+
+## Key Facts
+
+## Main Legal Or Contractual Questions
+
+## Risks And Unknowns
+
+## Professional Review Items
+
+## Sources
+```
+
+### Chronology
+
+```markdown
+| Date | Event | Evidence | Confidence | Review item |
+| --- | --- | --- | --- | --- |
+| YYYY-MM-DD |  | source.md chunk=0 | High/Medium/Low |  |
+```
+
+### Clause Review
+
+```markdown
+| Clause topic | Source | Extract summary | Risk | Follow-up |
+| --- | --- | --- | --- | --- |
+| Termination | contract.docx chunk=3 |  |  |  |
+```
+
+### Evidence Gap List
+
+```markdown
+| Missing or weak evidence | Why it matters | Suggested next document |
+| --- | --- | --- |
+|  |  |  |
+```
+
+## Final Response Checklist
+
+Before handing back the work:
+
+- state where the report was saved;
+- list source paths used, not private full passages;
+- mention unsupported, stale, or missing files;
+- include a professional-review section;
+- state whether the artifact is safe to commit or must remain local.

package/skills/ragmir-markdown-report/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: ragmir-markdown-report
+description: >-
+  Create a cited Markdown report from a Ragmir local knowledge base. Use when the user asks for a
+  report, dossier, audit memo, planning note, evidence summary, or Markdown deliverable grounded in
+  private repository documents indexed by Ragmir.
+---
+
+# Ragmir Markdown Report
+
+Use this skill to write a Markdown report from local Ragmir evidence without leaking raw documents.
+Generated reports are derived artifacts and should stay local unless the user explicitly decides a
+sanitized report is safe to commit or share.
+
+## Confidentiality Rules
+
+- Treat source documents, retrieved passages, notes, drafts, and generated reports as sensitive.
+- Prefer writing reports under `.ragmir/reports/`, which is ignored by Git when Ragmir is installed.
+- Do not commit generated reports by default.
+- Do not paste long raw passages into the report. Use summaries, short cited extracts when needed,
+  and source references.
+- Separate proven facts, inference, uncertainty, and missing evidence.
+- For legal, tax, medical, immigration, financial, or compliance reports, include a professional
+  review section instead of presenting the report as final advice.
+
+## 1. Verify The Knowledge Base
+
+From the repository root:
+
+```bash
+pnpm exec ragmir doctor
+pnpm exec ragmir audit
+pnpm exec ragmir security-audit
+```
+
+If files are missing, stale, or setup is incomplete:
+
+```bash
+pnpm exec ragmir doctor --fix
+pnpm exec ragmir audit --unsupported
+```
+
+Do not write a final report from stale evidence unless the user explicitly accepts that limitation.
+
+## 2. Build An Evidence Plan
+
+For a broad report, use multiple targeted retrieval passes instead of one generic query:
+
+```bash
+pnpm exec ragmir search "<main report topic>" --top-k 8
+pnpm exec ragmir search "<people, dates, amounts, obligations, risks, decisions>" --top-k 8
+pnpm exec ragmir ask "<specific synthesis question>" --top-k 8
+```
+
+When MCP is available, prefer `ragmir_search`, `ragmir_ask`, `ragmir_audit`, and
+`ragmir_security_audit` over shell commands.
+
+Keep a working note of source paths and chunk numbers for each claim you plan to include.
+
+## 3. Write The Report
+
+Default report structure:
+
+```markdown
+# <Report Title>
+
+## Scope
+
+## Executive Summary
+
+## Evidence Inventory
+
+## Findings
+
+## Risks And Open Questions
+
+## Recommended Next Actions
+
+## Sources
+```
+
+Use tables only when they make comparisons easier. Keep each finding tied to one or more source
+paths and chunk numbers when possible.
+
+## 4. Save Locally
+
+Create the report directory:
+
+```bash
+mkdir -p .ragmir/reports
+```
+
+Write the report to:
+
+```plain text
+.ragmir/reports/<subject-kebab>.md
+```
+
+If the user explicitly wants a tracked report, create a sanitized file outside `.ragmir/` and state
+which private details were excluded.
+
+## 5. Report The Result
+
+After writing the report, tell the user:
+
+- the report path;
+- whether the index was ready;
+- how many source paths were used;
+- any unsupported, stale, or missing files that weaken the report;
+- whether the report is safe to commit or should remain local.