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

clickhelp

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

Quality

Content

76%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 comprehensive CLI examples and a clear connection workflow, though destructive operations lack validation checkpoints and the inline actions table is long enough to merit a reference file. It is a strong, mostly executable skill body.

Suggestions

Add a validation/verification step for destructive or batch operations (e.g., run get-topic before delete-topic, or confirm the target ID with the user) so workflow_clarity can exceed the cap of 3.

Move the lengthy Popular actions table into a references/actions.md file and link to it from a short "Key actions" summary, improving progressive disclosure and token efficiency.

Trim the introductory "ClickHelp is a browser-based documentation tool..." paragraph and conversational phrases like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and tables with little concept over-explanation, but the opening "browser-based documentation tool" intro and a few prose flourishes ("focus on the integration logic rather than auth plumbing") could be trimmed, matching the score-4 anchor.	4 / 5
Actionability	It provides copy-paste-ready bash commands for install, auth, connection, action search/run, and proxy requests, plus comprehensive action and flag tables covering common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based branching and a re-poll feedback loop, but destructive/batch actions (delete-topic, delete-user, change-publication-visibility) lack validation steps, capping workflow_clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	With no bundle files present, all content is inline but well-organized under clear section headers (Overview, Working with ClickHelp, Popular actions, Proxy, Best practices); structure is good with only minor organization gaps, fitting the score-4 anchor.	4 / 5
	Total	16 / 20 Passed

Description

57%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 is adequately scoped to ClickHelp and includes a usable 'Use when' trigger, but its action list is generic and its trigger terms lack natural synonyms or file extensions. It is functional but could be sharpened to reduce ambiguity and conflict risk.

Suggestions

Replace generic verbs with concrete ClickHelp actions, e.g. "Create and update topics, manage TOC structure, publish projects, export publications to PDF/Docx/WebHelp."

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user mentions ClickHelp, online help manuals, knowledge bases, user guides, or wants to author/publish documentation."

Drop the vague "Manage data, records, and automate workflows" phrasing, which overlaps with many data-oriented skills and weakens distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the ClickHelp domain and offers action verbs ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete ClickHelp operations, matching the score-2 anchor.	2 / 5
Completeness	It states a (vague) 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with ClickHelp data"), matching score-4 where both are present but the when could be more specific.	4 / 5
Trigger Term Quality	It includes "ClickHelp data" plus generic terms (data, records, workflows) but lacks common natural variations or synonyms users would say, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Scoping to the named ClickHelp app gives a mostly-distinct niche with only minor overlap risk against closely related documentation/data skills, fitting the score-4 anchor.	4 / 5
	Total	13 / 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/clickhelp/SKILL.md
Commit: f484c82

Reviewed: ~10 hours 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.