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

helpdocs

HelpDocs integration. Manage data, records, and automate workflows. Use when the user wants to interact with HelpDocs 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

78%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 highly actionable with executable commands and a sensible connection workflow including state-checkpoints. It is slightly held back by minor redundancy and by inlining advanced reference material rather than progressively disclosing it.

Suggestions

Move the detailed clientAction object spec and the proxy flags table into a separate reference file (e.g. REFERENCE.md) and link to it from the overview.

Remove the duplicated `membrane action list` invocation in 'Popular actions' or consolidate it with the earlier 'Searching for actions' example.

Fix the 'skip to Step 2' reference by labeling the post-connection step as Step 2 so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and short explanations, but includes some light prose (e.g. 'so you can focus on the integration logic rather than auth plumbing') and a near-duplicate `membrane action list` command in 'Popular actions'.	4 / 5
Actionability	Provides copy-paste ready, executable commands throughout (install, login, connection ensure/get, action list/run, request proxy) with flags and a clear options table covering the common cases.	5 / 5
Workflow Clarity	Clear sequence from install → authenticate → connect → poll for READY → search → run, with explicit state-handling checkpoints and a re-poll feedback loop; minor gap is the dangling 'skip to Step 2' reference with no labeled Step 2.	4 / 5
Progressive Disclosure	Well-sectioned single file with no bundle files, but advanced detail (the clientAction spec, proxy flag table) is inlined rather than split into one-level-deep references, and the 157-line body is heavier than an overview-first structure.	3 / 5
	Total	16 / 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 answers both what and when and is anchored to a specific brand, making it reasonably distinct. Its main weakness is generic action language ('manage data, records') and limited trigger-term variety.

Suggestions

Replace generic verbs with concrete HelpDocs actions, e.g. 'Create and update articles, categories, and revisions; manage teams and users.'

Add natural trigger phrases users would say, e.g. 'Use when the user mentions HelpDocs, help articles, knowledge base, or documentation sites.'

Keep the 'Use when...' clause but tie it to specific HelpDocs objects (articles, categories, projects) rather than 'data'.

Dimension	Reasoning	Score
Specificity	Names the HelpDocs domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not comprehensive.	3 / 5
Completeness	Both 'what' (HelpDocs integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with HelpDocs data') are present, though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'HelpDocs' and 'interact with HelpDocs data', but lacks synonyms or variations users might say beyond the brand name.	3 / 5
Distinctiveness Conflict Risk	The HelpDocs brand name gives it a clear niche with distinct triggers and low conflict risk, though the generic 'manage data' phrasing leaves minor overlap with broad data-management skills.	4 / 5
	Total	14 / 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/helpdocs/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.