Name: linearb
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

linearb

LinearB integration. Manage Organizations. Use when the user wants to interact with LinearB data.

Quality

60%

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

Quality

Content

57%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 actionable and CLI-driven with a solid connection workflow, but it is padded with platform exposition, lacks validation steps for its destructive/batch operations, and inlines a large reference table that should be split out. Tightening the prose and adding verification guidance would raise the score.

Suggestions

Add explicit validation/verification steps for destructive and batch actions (e.g., list the resource and confirm with the user before running delete-* or bulk-create-services).

Move the Popular actions table into a separate reference file (e.g., references/actions.md) and link to it from the body to improve progressive disclosure.

Cut the opening platform-explainer paragraph and marketing language ("focus on the integration logic rather than auth plumbing") to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI-focused content, but it opens with platform-explainer prose ("LinearB is a software development analytics platform... It provides insights into metrics like cycle time...") and marketing-style lines ("so you can focus on the integration logic rather than auth plumbing") that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready CLI commands (install, login, connection ensure, action run, request) plus a concrete action-key table covering common cases, with only minor placeholder gaps (CONNECTION_ID, <actionId>) keeping it from the top anchor.	4 / 5
Workflow Clarity	The connection flow has a polling feedback loop and state checkpoints, but destructive and batch operations (delete-user/team/service, bulk-create-services, create-users) are listed with no validation or verification guidance, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The body is reasonably sectioned, but it is a single ~180-line file with a large 20-row inlined actions table that clearly belongs in a separate reference file, and there are no bundle files to split content into.	3 / 5
	Total	13 / 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 is clear, third-person, and names a distinct LinearB niche with a usable trigger clause, but it is thin on concrete capabilities and natural trigger variations. Expanding the action list and trigger phrasing would lift it into the top band.

Suggestions

List 3-5 concrete capabilities (e.g., list/manage teams, services, deployments, incidents) instead of only "Manage Organizations".

Broaden the trigger clause with natural variations, e.g., "Use when the user wants to query or manage LinearB teams, services, deployments, or incidents".

Avoid the generic "LinearB integration" opener; lead with the concrete actions the skill performs.

Dimension	Reasoning	Score
Specificity	Names the domain ("LinearB integration") and one concrete action ("Manage Organizations"), but offers only a single action rather than a comprehensive list, matching the 1-2-concrete-actions anchor.	3 / 5
Completeness	States both what it does ("Manage Organizations") and when to use it ("Use when the user wants to interact with LinearB data"), but the trigger clause is generic and could be more explicit, so it sits just below the top anchor.	4 / 5
Trigger Term Quality	Includes relevant keywords ("LinearB", "Organizations", "LinearB data") and a natural trigger phrase, but misses common synonyms and variations a user might actually say, fitting the some-keywords-but-incomplete anchor.	3 / 5
Distinctiveness Conflict Risk	The LinearB-specific niche is clear and unlikely to trigger for unrelated skills, but the thin set of triggers keeps it from a minimal-conflict top score.	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/linearb/SKILL.md
Commit: f484c82

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