Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When the user needs to read or search their own notes from Monologue Notes via API (read-only), especially listing, filtering, or fetching full note content.
MONOLOGUE_API_KEY as bearer token via Authorization header, never expose it.GET /v1/public-api/notes or /notes/{note_id} with curl/jq.Structured JSON note data (summaries, transcripts) retrieved securely for user review or downstream local processing.
Use Cases
A researcher wants to find all notes containing 'interview' from the last quarter. They use this skill to call the list endpoint with q and created_after filters via curl, then pipe to jq for clean output. It solves the problem of manually digging through notes and delivers a filtered, structured list quickly.
A user needs the full transcript of a specific meeting note for summarization. They use the get-single-note endpoint with the note_id, retrieve JSON via curl, and extract transcript with jq. This avoids UI navigation and provides machine-readable data ready for downstream processing.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File