Name: newscatcher
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

newscatcher

NewsCatcher integration. Manage Topics. Use when the user wants to interact with NewsCatcher data.

Quality

66%

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/newscatcher/SKILL.md

Quality

Content

67%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 a well-structured, largely executable guide to driving NewsCatcher through the Membrane CLI with a real connection-state feedback loop, weakened mainly by a padded overview paragraph and a couple of loose cross-references.

Suggestions

Trim the opening NewsCatcher overview and the "so you can focus on the integration logic" framing; Claude can infer what a news API is for.

Resolve the dangling "Step 2" reference and fix the inconsistent "1b" numbering so the connection workflow reads as a single coherent sequence.

Add one end-to-end worked example with realistic NewsCatcher parameters (e.g. an article search intent and --input JSON) to lift actionability from concrete commands to fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening overview paragraph ("NewsCatcher is a news aggregation API... It's useful for anyone needing to programmatically access and analyze news content") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests with a flags table; minor gaps remain since NewsCatcher-specific actions (Search, Get Article Text) are not shown with real parameter examples.	4 / 5
Workflow Clarity	There is a clear sequence (install → auth → connect → search → run → proxy) with a genuine feedback loop around connection state (poll --wait, handle CLIENT_ACTION_REQUIRED, re-poll), but a dangling "Step 2" reference and loose 1b numbering leave minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist, and the single SKILL.md is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); not a 5 because at ~140 lines some referenceable detail (the proxy flags table, clientAction handling) could be split out.	4 / 5
	Total	15 / 20 Passed

Description

66%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 answers both what and when and is clearly tied to a distinct named product, but its action list is thin and it lacks the natural news-related trigger terms users would actually say.

Suggestions

Add concrete actions beyond "Manage Topics" (e.g. search news articles, extract article text, summarize articles) to raise specificity.

Include natural user-facing trigger phrases like "search news", "find news articles", or "summarize articles" rather than only the generic "interact with NewsCatcher data".

Tighten the when-clause to name the concrete scenarios (e.g. "Use when the user wants to search, summarize, or extract text from news articles").

Dimension	Reasoning	Score
Specificity	The phrase "Manage Topics" names the domain (NewsCatcher) and one concrete action targeting a NewsCatcher entity, but coverage is not comprehensive — only one action verb is given.	3 / 5
Completeness	Both a what ("NewsCatcher integration. Manage Topics.") and an explicit when ("Use when the user wants to interact with NewsCatcher data.") are present; not a 5 because the when-trigger is generic rather than concrete phrases.	4 / 5
Trigger Term Quality	It includes "NewsCatcher" and "Topics" as relevant keywords but omits the natural phrases a user would actually say (e.g. "news articles", "search news", "find articles"), so common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The description names a specific third-party product (NewsCatcher) twice and ties triggers to "NewsCatcher data", giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/newscatcher/SKILL.md
Commit: f484c82

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.