linear-issue-generator
Linear Issue Generator - Auto-activating skill for Enterprise Workflows. Triggers on: linear issue generator, linear issue generator Part of the Enterprise Workflows skill category.
35
3%
Does it follow best practices?
Impact
92%
0.94xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/linear-issue-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely thin—it essentially restates the skill name without explaining what the skill does or when it should be used. It lacks concrete actions, meaningful trigger terms, and an explicit 'Use when...' clause, making it nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Linear issues with title, description, priority, assignee, and team fields from user requirements or bug reports.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks to create a ticket in Linear, file a bug, log a feature request, or mentions Linear issues/tasks.'
Include natural keyword variations users might say, such as 'Linear ticket', 'create issue', 'file bug in Linear', 'Linear task', '.linear', to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Linear Issue Generator') but provides no concrete actions. It does not describe what the skill actually does—no mention of creating issues, setting fields, assigning teams, or any specific capabilities. | 1 / 3 |
Completeness | The 'what' is essentially absent beyond the name, and the 'when' is only a redundant trigger phrase with no explicit 'Use when...' clause describing scenarios or user intents that should activate this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'linear issue generator' repeated twice. There are no natural user keywords like 'create linear ticket', 'file a bug', 'add issue to Linear', 'linear task', etc. Users would rarely say 'linear issue generator' verbatim. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Linear' as a specific product gives it some distinctiveness from generic issue/ticket skills, but the lack of detail about what it does versus other Linear-related skills or general issue tracking skills leaves moderate overlap risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—a template placeholder that contains no actual instructions, code, or actionable guidance for generating Linear issues. It repeatedly references 'linear issue generator' without ever explaining what to do, how to call the Linear API, what fields to populate, or how to validate results. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to create Linear issues via the Linear API (e.g., GraphQL mutations with specific fields like title, description, teamId, priority, labels).
Define a clear workflow: gather requirements → construct issue payload → call Linear API → validate response → handle errors, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual instructions and examples.
Include a quick-start section with a copy-paste-ready API call or SDK usage example, and link to a separate reference file for advanced patterns like bulk issue creation or template-based generation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information about 'linear issue generator' without adding substance. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no API calls, no concrete steps, no examples of Linear issue payloads or configurations. The 'Capabilities' section lists abstract promises ('provides step-by-step guidance') without delivering any actual guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to detailed files, no structured navigation, and no separation of overview from detailed content. There is nothing to progressively disclose because there is no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
dc559db
- Reviewed
Table of Contents
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.