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 and template-like, providing almost no useful information beyond the skill's name. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select it. The repeated trigger term and boilerplate category mention add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Linear issues with titles, descriptions, labels, priorities, and team assignments from user requirements or bug reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a ticket in Linear, file a Linear issue, log a bug in Linear, or generate Linear tasks from requirements.'
Remove the redundant duplicate trigger term and replace with varied natural phrases users might say, such as 'linear ticket', 'create issue in linear', 'linear bug report', 'linear task'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Linear Issue Generator') but does not describe any concrete actions. There is no mention of what the skill actually does—no verbs like 'creates issues', 'assigns labels', 'sets priorities', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is limited to a redundant trigger phrase with no explicit 'Use when...' clause or meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'linear issue generator' repeated twice. There are no natural user keywords like 'create linear ticket', 'file a bug in Linear', 'Linear task', or other variations a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Linear' as a specific tool provides some distinctiveness from generic issue/ticket skills, but the lack of concrete actions or scope means it could still overlap with other Linear-related or issue-tracking skills. | 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 essentially a placeholder template with no real content. It contains no actionable instructions, no code examples, no API references, and no workflow for generating Linear issues. Every section repeats the phrase 'linear issue generator' without providing any concrete guidance on how to actually create issues in Linear.
Suggestions
Add concrete, executable code examples showing how to create Linear issues via the Linear API (e.g., GraphQL mutations with authentication setup)
Define a clear step-by-step workflow: authenticate → gather issue details → create issue → validate response → handle errors
Include specific field mappings and examples (title, description, team, priority, labels, assignee) with sample input/output
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual implementation guidance
| 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 API usage or issue creation. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The content merely states it 'provides step-by-step guidance' without including any actual steps. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no quick-start section with real content, and no navigation to deeper resources. The sections are superficial headers over empty 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
4dee593
- 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.