Name: backlog
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

backlog

Backlog integration. Manage Projects. Use when the user wants to interact with Backlog data.

Quality

65%

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

Quality

Content

68%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 copy-paste CLI commands and a well-structured connection workflow, but it carries some filler and lacks validation guidance for destructive Backlog operations. Organization is solid for a single-file skill.

Suggestions

Remove filler (e.g., "Use action names and parameters as needed.") and either populate or drop the empty Description column in the Popular actions table.

Add a validation/confirmation step before destructive actions (e.g., confirm issue state or list-before-delete for delete-issue) to lift workflow clarity past the destructive-cap of 3.

Clarify the "skip to Step 2" references by explicitly labeling Step 1 and Step 2 sections so the connection-to-action flow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes filler ("Use action names and parameters as needed"), explanatory fluff about auth plumbing, and a Popular actions table with empty description columns, fitting the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	Commands like `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://backlog.com/" --json`, and `membrane action run <actionId> ... --input '{...}'` are copy-paste ready and cover the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has clear state-checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling, but destructive actions like delete-issue lack any validation or confirmation step, so the destructive-operation cap of 3 applies even though the connection sequence is otherwise strong.	3 / 5
Progressive Disclosure	No bundle files are present and the single SKILL.md is organized into clear, well-signaled sections with no nested references, but the inlined Popular actions and proxy-flag tables represent minor organization gaps rather than a perfectly split overview.	4 / 5
	Total	15 / 20 Passed

Description

61%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 cleanly states a specific integration niche and includes an explicit use-when clause, but its capability statement is thin and trigger term coverage is narrow. It is distinct but only modestly specific.

Suggestions

Replace the generic "Manage Projects" with 2-3 concrete actions (e.g., create/update/delete issues, list projects, add comments) to lift specificity.

Add natural trigger synonyms users say (e.g., "Backlog issues", "Backlog tasks", "Backlog projects") to broaden trigger term coverage.

Tighten the when-clause with concrete triggers like "Use when the user wants to manage Backlog issues, projects, or comments."

Dimension	Reasoning	Score
Specificity	"Manage Projects" names the Backlog domain but the single action is minimal and generic, matching the anchor for naming a domain with minimal actions rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	Both what ("Backlog integration. Manage Projects.") and when ("Use when the user wants to interact with Backlog data") are explicitly present, with the when clause explicit but generic, matching the 4 anchor above the weakly-implied 3.	4 / 5
Trigger Term Quality	"Backlog", "Backlog data", and "Projects" are relevant natural terms, but coverage lacks common variations or synonyms, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Backlog is a specific named application with a distinct trigger ("interact with Backlog data"), giving a clear niche with minimal conflict risk against other skills.	5 / 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/backlog/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.