CtrlK
BlogDocsLog inGet started
Tessl Logo

newsapi

NewsAPI integration. Manage Articles, Sources. Use when the user wants to interact with NewsAPI data.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/newsapi/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable with executable commands and good connection-state validation, and it is well-structured. Its main weakness is conciseness: the introductory paragraph over-explains NewsAPI, which Claude already knows.

Suggestions

Trim the opening "NewsAPI is a service that provides programmatic access..." paragraph to a single line, since Claude already knows what NewsAPI is.

DimensionReasoningScore

Conciseness

The command examples are lean, but the opening paragraph ("NewsAPI is a service that provides programmatic access to news articles...") explains what NewsAPI is and a few transitional sentences ("so you can focus on the integration logic rather than auth plumbing") add padding Claude does not need, fitting score 3 (mostly efficient with some unnecessary explanation).

3 / 5

Actionability

It provides fully executable, copy-paste-ready CLI commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a flags table, covering the common cases with explicit placeholders.

5 / 5

Workflow Clarity

The install→auth→connect→search→run flow is clear, and the connection step has explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a feedback loop (poll again after the user acts); it is not score 5 because the macro steps are implicit rather than a numbered, checkpointed sequence.

4 / 5

Progressive Disclosure

The body is well-organized into clear headed sections with no broken or nested references, but everything is inlined in a single SKILL.md with no one-level-deep references, so it is good structure (score 4) rather than exemplary content splitting (score 5).

4 / 5

Total

16

/

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 has a clear niche and includes both a what and a when, but its actions are generic and its trigger terms miss common natural phrasings like "headlines" or "top news". Strengthening the verb and trigger phrases would lift the weaker dimensions.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Search news articles, fetch top headlines, list news sources".

Expand the "Use when" clause with natural trigger phrases users actually say, such as "headlines", "top news", or "breaking news".

DimensionReasoningScore

Specificity

"Manage Articles, Sources" names the domain and two concrete resource types, but the single verb "Manage" is generic and the action coverage is not comprehensive, fitting the score-3 anchor rather than the multi-action score-4/5 anchors.

3 / 5

Completeness

It provides both a "what" ("NewsAPI integration. Manage Articles, Sources.") and a "when" ("Use when the user wants to interact with NewsAPI data"), but the trigger clause is generic and circular rather than listing concrete triggers, so it is not the explicit score-5 level.

4 / 5

Trigger Term Quality

It includes "NewsAPI", "Articles", "Sources", and "NewsAPI data", but misses common natural phrasings a user would actually say such as "headlines", "top news", or "breaking news", so it lands at score 3 (some relevant keywords, missing common variations).

3 / 5

Distinctiveness Conflict Risk

It is tied to a specific named product (NewsAPI) with distinct triggers (NewsAPI, Articles, Sources), giving it a clear niche and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.