Menu
Pull Modjo call summaries and full transcripts for a date range and topic, structured for downstream investigation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review a PRD against Kalina's seven review criteria. For each criterion, flag specific lines that pass or fail with line numbers and push back with a concrete question. Output goes to reviews/{prd-name}-review-{date}.md.
Walk a PM through writing a PRD against the generic template, asking one question per section and drafting based on the answer. Pulls evidence from a finding doc as it goes.
Walk through a PRD from an engineering lead's lens, surfacing implementation ambiguities and missing technical requirements. Uses the AskUserQuestion tool to interview the PM one question at a time, then writes the resolved answers into the PRD as a clarifying-questions appendix.
Turn a feature passport into customer-facing release notes — headline, what shipped, what changes in the customer's workflow, links.
| name | modjo-pull |
| description | Pull Modjo call summaries and full transcripts for a date range and topic, structured for downstream investigation. |
| when-to-use | Any time you need fresh customer-call evidence for an investigation. Skip the manual export — this skill keeps the structure consistent across pulls so codebooks and findings don't break. |
Wraps the Modjo API. Modjo doesn't have a native MCP server; this skill calls the API directly and saves results in a consistent shape.
date_range: ISO 8601 date range (e.g. 2026-04-01:2026-04-15)topic: free-text topic filter passed to the Modjo search endpoint (e.g. "quote tracking")Reads MODJO_API_TOKEN from the local .env file. This token is not committed to the repo — set it locally before running.
https://api.modjo.ai/v1/calls/search with { from, to, query }./calls/{id} and /calls/{id}/transcript.data/modjo/{date}/{call-id}.json with:
summary — Modjo's AI summarytranscript — full transcript with speaker turns and timestampsparticipants — array of { name, role, company }date — ISO datetimelanguage — nl | en | mixeddata/modjo/{date}/manifest.json listing what was pulled.data/modjo/2026-04-15/. Only re-run this skill if you need fresher calls.This is the pattern to reach for when a tool doesn't have a native MCP. Wrap the API as a skill, save results to a consistent path under data/, and treat the skill as if it were an MCP. From the user's perspective the experience is identical — /modjo-pull just works. Other candidates for the same treatment: tools where MCPs are still maturing, or where the team needs auth scoped to the repo rather than to a desktop session.