paperclip-task-bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

Quality

73%

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 ./packages/adapters/hermes/skills/paperclip-task-bridge/SKILL.md

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and highly actionable with concrete curl and node commands, but workflow guidance lacks explicit validation feedback loops for its mutating operations, and the referenced helper script is not provided in a bundle directory.

Suggestions

Add an explicit validate-and-retry step for mutating commands, e.g. confirm task creation succeeded (check the returned issue id) and retry on error before proceeding.

Ship paperclip-task.mjs in the scripts/ bundle (or a references/ guide) so the referenced --help surface actually exists alongside the skill.

Consider a short references/ doc for the full flag set or status-value semantics if the helper grows, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is lean—tight env-var lists, a curl example, and concrete commands with no filler explaining what Paperclip or Hermes are—assuming Claude's competence throughout.	3 / 3
Actionability	It provides a fully executable curl key-creation command and copy-paste-ready node invocations with real flags (--parent-id, --issue, --status, --description-file, --body-file -).	3 / 3
Workflow Clarity	A Workflow Expectations section lists sequenced guidance and a list-before-duplicate checkpoint, but mutating operations (create/update/comment) lack an explicit validate->fix->retry feedback loop, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	Sections are well organized, but the skill references an external helper (paperclip-task.mjs via --help) that is not present in a bundle directory, and there are no one-level-deep reference docs signaled.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinct, naming four concrete Paperclip-task actions with a credential scope, but it omits an explicit "Use when" trigger clause and relies on product-internal vocabulary, which limits trigger-term quality and caps completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when a Hermes-originated request must create, comment on, update, or list Paperclip tasks."

Broaden trigger-term coverage with natural phrasings users would say, such as "task tracking", "create a task", or "update ticket status".

Keep the third-person voice and concrete actions but avoid assuming users will already name Paperclip/Hermes.

Dimension	Reasoning	Score
Specificity	"Create, comment on, update, and list" names four concrete actions against the Paperclip-tasks domain with a credential constraint, matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks any explicit "Use when..." trigger in the description itself; per the rubric a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "Paperclip tasks", "Hermes", "comment", "update", "list" are relevant but product-internal with no common variations or natural user phrasings, landing at the some-keywords anchor rather than broad coverage.	2 / 3
Distinctiveness Conflict Risk	"Paperclip tasks from Hermes" with "scoped Paperclip API credentials" and "task_bridge" defines a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: paperclipai/paperclip
Path: packages/adapters/hermes/skills/paperclip-task-bridge/SKILL.md
Commit: 14f20be

Reviewed: 4 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.