monologue-notes-api

Use this skill when the user wants to read or search their Monologue notes through the Monologue Notes REST API. It covers authentication with the MONOLOGUE_API_KEY environment variable, safe token handling, listing notes, fetching a single note, pagination, filters, and error handling. The API is read-only and should be accessed with direct HTTP requests such as curl or any equivalent REST client.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, well-structured read-only API skill with executable curl examples, clear sequencing for pagination, and a sensible auth check. It is concise without padding, with only minor opportunities to tighten examples and add an explicit auth-failure recovery loop.

Suggestions

Add a short retry/recovery note for 401/403 (re-check MONOLOGUE_API_KEY presence/scope before retrying) to give the pagination and request workflows an explicit feedback loop.

Tighten the 'Avoid commands such as these' block to a single representative example plus the rule, to reclaim a little token budget.

Consider moving the full per-endpoint parameter/error reference into a references file and keeping only the quick-start examples inline, which would let progressive_disclosure reach the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding about what REST or curl is — but a few sections (the three-line 'Avoid commands such as these' block and a near-duplicate base request pattern) could be trimmed, so it sits just below the fully-lean anchor.	4 / 5
Actionability	Copy-paste-ready curl commands cover every common case (list, get single note, search, paginate, time-filter) with jq variants, concrete query parameters, and per-endpoint error codes.	5 / 5
Workflow Clarity	Multi-step workflows are clearly sequenced — pagination is a numbered 1–4 list with an explicit stop condition, and auth has a validation checkpoint (check token presence before calling) — but there is no explicit retry/recovery loop for 401/403, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Authentication, Base URL, Request Pattern, Endpoints, Common Workflows, Operating Rules) with no nested references, and no bundle files exist to misreference; it is slightly above the 'good structure' anchor though the full endpoint reference is inline rather than split out.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete capabilities and gives an explicit 'Use when' trigger tied to a distinct product. Voice stays appropriately third-person; only minor keyword-synonym coverage keeps it from a perfect sweep.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'authentication with the MONOLOGUE_API_KEY environment variable, safe token handling, listing notes, fetching a single note, pagination, filters, and error handling' — giving comprehensive coverage of the API's operations rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' (covers auth, listing, fetching, pagination, filters, error handling, read-only) and 'when' ('Use this skill when the user wants to read or search their Monologue notes through the Monologue Notes REST API') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural phrases a user would say are present ('read or search their Monologue notes', 'Monologue Notes REST API', 'curl'), but a few common variations/synonyms (e.g. 'browse', 'find', 'look up') are missing, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly named, narrow product (Monologue Notes REST API) with distinct triggers, so the risk of firing for an unrelated skill is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: intellectronica/agent-skills
Path: plugins/monologue-notes-api/skills/SKILL.md
Commit: 9b0e00a

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.