Name: hashnode
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hashnode

Hashnode integration. Manage Users, Publications. Use when the user wants to interact with Hashnode data.

Quality

70%

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

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 concrete executable commands and a well-sequenced connection workflow including polling checkpoints. Its main weakness is mild verbosity in the introductory prose and some content that could be split into reference files.

Suggestions

Trim the introductory paragraph explaining what Hashnode is and the "focus on integration logic rather than auth plumbing" aside, which Claude does not need.

Label the post-connection section explicitly as "Step 2" or remove the dangling "skip to Step 2" reference so the workflow reference resolves.

Consider moving the proxy flag table and popular-actions table into reference files to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but the intro ("Hashnode is a blogging platform specifically designed for developers...") and phrases like "so you can focus on the integration logic rather than auth plumbing" explain things Claude already knows, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (connection ensure, action list/run, request proxy) with flags and a JSON-parameter example, covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based branching and polling feedback loops (BUILDING -> READY, poll again after CLIENT_ACTION_REQUIRED), but the "skip to Step 2" reference points to a step that is not explicitly labeled, leaving a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist; the single file is well-organized into clear sections with tables, and there are no nested references, but the skill exceeds 50 lines so the simple-skill exception does not fully apply and some inline content (proxy flags, action tables) could live in separate files.	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 clearly identifies the Hashnode niche and includes an explicit "Use when" trigger, but its action verb is generic and its trigger terms lack common synonyms like posts or articles. It is solid but could be more specific and comprehensive.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List and read posts, manage users and publications, add comments."

Expand trigger terms to include natural synonyms users say, such as posts, articles, blogs, and followers.

Tighten the "Use when" clause with concrete triggers, e.g. "Use when the user wants to read or publish Hashnode posts, or manage users and publications."

Dimension	Reasoning	Score
Specificity	"Manage Users, Publications." names the domain and two concrete entities, but "Manage" is a generic verb rather than a specific action, so it sits between the generic-actions (2) and concrete-actions (3) anchors.	3 / 5
Completeness	It has both a clear "what" ("Hashnode integration. Manage Users, Publications.") and an explicit "when" ("Use when the user wants to interact with Hashnode data."), but the trigger clause is generic rather than listing concrete trigger phrases, fitting the 4 anchor.	4 / 5
Trigger Term Quality	Phrases like "Hashnode", "Users", "Publications", and "Hashnode data" give relevant keywords, but common variations a user would say (posts, articles, blogs) are missing, matching the anchor with some-but-incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Hashnode integration" names a specific platform niche with distinct triggers and minimal overlap risk with 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/hashnode/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.