Name: scoopit
Rating: 48.8 (1 reviews)
Author: membranedev

scoopit

Scoop.it integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scoop.it data.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/scoopit/SKILL.md

Quality

Content

60%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 content is genuinely actionable with copy-paste CLI commands and a useful flag reference, but it spends tokens explaining Scoop.it's marketing purpose and stops the connection workflow at polling without explicit validation/error-recovery guidance. Tightening the prose and adding verification checkpoints would lift both conciseness and workflow clarity.

Suggestions

Add an explicit validation/error-recovery checkpoint to the connection polling loop, e.g. 'If CLIENT_ACTION_REQUIRED persists after the user acts, re-check the clientAction instructions; on CONFIGURATION_ERROR, surface the error field before retrying.'

Trim the introductory marketing paragraph about what Scoop.it is — Claude can infer the product's purpose; keep only what's needed to act.

Fix the step numbering (a referenced 'Step 2' with no 'Step 1', and a '1b' with no '1a') so the connection workflow reads as a coherent sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but it pads with content Claude already knows — the opening line explaining what Scoop.it is and its marketing purpose, and explanatory prose around the connection state machine that could be tightened.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request) with flag tables and JSON usage; minor gaps are placeholders like CONNECTION_ID and the 'QUERY' intent that need substitution.	4 / 5
Workflow Clarity	The connect-to-poll-to-ready sequence is laid out, but it involves a poll loop over external state with no explicit validation/error-recovery checkpoint (e.g. what to do on repeated CLIENT_ACTION_REQUIRED or timeout), and the destructive proxy/delete operations lack verification steps, capping this at 3 per the feedback-loop guideline.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to over-split; minor gaps are a 'Step 2' referenced before any numbered Step 1 and a '1b' subsection with no '1a'.	4 / 5
	Total	14 / 20 Passed

Description

46%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 correctly identifies the product and includes a 'Use when' trigger, but it relies on generic action verbs and misses the natural curate/publish/scoop phrasings users would actually say. Trigger-term quality is the weakest dimension and is the main thing keeping the score mid-range.

Suggestions

Replace generic verbs with concrete Scoop.it capabilities, e.g. 'Discover, curate, and publish content on topics; manage scoops and topic suggestions.'

Add natural trigger terms a user would say, such as 'curate content', 'publish a topic', or 'scoop a page', mirroring the good-example pattern of listing what the user mentions.

Make the 'Use when' clause specific to Scoop.it intent, e.g. 'Use when the user wants to curate, publish, or manage content on Scoop.it.'

Dimension	Reasoning	Score
Specificity	It names the domain (Scoop.it) and two concrete action clusters ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than enumerated capabilities like create/edit/delete, so coverage is not comprehensive.	3 / 5
Completeness	It has a clear 'what' (Scoop.it integration managing data/records/workflows) and an explicit 'Use when...' clause, but the 'when' references only 'interact with Scoop.it data' broadly rather than concrete trigger phrases, which the guideline says caps completeness at 3 only when the 'when' is weakly implied — here it is explicit but thin.	3 / 5
Trigger Term Quality	The only natural keyword is 'Scoop.it' plus generic phrases ('Manage data, records, automate workflows'); it lacks the natural phrasings a user would say (e.g. 'curate content', 'publish a topic', 'scoop a page') and any file/resource triggers.	2 / 5
Distinctiveness Conflict Risk	Tying the skill to a named third-party product (Scoop.it) gives it a clear niche with minimal conflict risk against unrelated skills, though 'Manage data, records, and automate workflows' is broad enough to overlap slightly with generic data-integration skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/scoopit/SKILL.md
Commit: f484c82

Reviewed: 4 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.