CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

notcrawl

Notion archive: desktop/API sync, Markdown export, page search, read-only SQL.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

The body is an exemplary lean, fully executable overview: concrete commands, explicit help pointers, and a clearly sequenced workflow with a freshness checkpoint and reporting requirements. The only meaningful gap is a missing post-sync verification step for its batch operations.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: "Use this for local Notion archive questions. Desktop reads local cache; API sync needs NOTION_TOKEN and page access." Every line is a path, command, or workflow step with no padding or explanations of known concepts, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Commands are copy-paste ready and cover the common cases: `notcrawl sync --source desktop`, `notcrawl search --limit 20 "query"`, `notcrawl sql "select count(*) from pages;"`, `notcrawl export-md`, plus explicit `--help` pointers for full syntax. Matches the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The 4-step Query Workflow is clearly sequenced with a leading freshness checkpoint and a reporting step ("Report date spans, page/database IDs, counts, and source limits"), matching the 'clear sequence with most checkpoints present; minor validation gaps' anchor. Not 5 because sync/export-md are batch operations with no post-operation verification step (e.g., re-running `notcrawl status` after sync); not 3 because a freshness checkpoint and source-limit caveats are explicitly present.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into clear sections (Sources, Refresh, Query Workflow). Per the guideline, a short skill with no need for external references scores 5 with well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

62%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.

The description is specific and distinctive, naming four concrete capabilities in a well-defined niche, but it entirely lacks a 'when to use' trigger clause and natural trigger phrasing that users would say. Adding an explicit 'Use when...' sentence with common synonyms would resolve the completeness and trigger-term gaps.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks about Notion pages, exporting Notion content to Markdown, or querying a local Notion archive."

Include natural synonyms such as "Notion workspace", "Notion database", and "export Notion" in the trigger phrasing so common user phrasings match.

Optionally surface the freshness/refresh capability (doctor/status/sync) in the description so the sync-maintenance use case is discoverable from the description alone.

DimensionReasoningScore

Specificity

"desktop/API sync, Markdown export, page search, read-only SQL" lists four concrete actions in the Notion-archive domain, matching the 'several specific actions; minor gaps' anchor. Not 5 because the telegraphic compression leaves minor coverage gaps (e.g., refresh/diagnostics workflow not surfaced); clearly above 3 since more than 1-2 actions are named.

4 / 5

Completeness

The 'what' is clear and multi-part (sync, export, search, SQL) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

"Notion" is the natural term a user would say, but common variations and trigger phrases ("Notion pages", "export Notion", "Notion workspace/database") are absent, matching the 'some relevant keywords but missing common variations' anchor. Not 4 because no explicit natural trigger phrasing is present at all.

3 / 5

Distinctiveness Conflict Risk

"Notion archive" carves out a clear niche with operations (cache sync, page search, read-only SQL) that no generic skill would claim, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor. Not 4 because overlap risk is negligible rather than minor.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

steipete/agent-scripts

Path

skills/notcrawl/SKILL.md

Reviewed

Table of Contents

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.