SKILLEMALL.ai

AC readwise

Manage Readwise highlights, books, daily review, and Reader documents (save-for-later / read-it-later). Use when the user wants to save articles or URLs to Reader, browse their reading list, search saved documents, review highlights, create or manage highlights and notes, check their daily review, list books/sources, or interact with Readwise/Reader in any way.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files · 1 script body ≈ 700 tokens Open the sourcegithub.com analyzed 2 d ago

Manage Readwise highlights, books, daily review, and Reader documents (save-for-later / read-it-later).

As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

AnalyzerWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
99
Quality 40%
94
Run on models
none yet
Process rating
C
60/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Exfiltration net-credential-use scripts/readwise.sh:21
      Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)
      [[ -n "${READWISE_TOKEN:-}" ]] || die "READWISE_TOKEN env var is not set. Get one at https://readwise.io/access_token"
      vendor-hostquoted

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 60/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (readwise) differs from the folder (readwise-api)
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 4 steps
    • 100Execution cost. Instruction body is 700 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +3Description length 363: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 4 items
    • +3Output format is stated explicitly
    • +4Has examples (8 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.