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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill linear-issue-generatorActivation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, mentions a vague category ('Enterprise Workflows'), but fails to describe what the skill actually does or when Claude should use it. The description would be nearly useless in a collection of 10+ skills.
Suggestions
Add concrete action verbs describing what the skill does (e.g., 'Creates Linear issues from requirements, converts bug reports to tickets, assigns team members and sets priorities').
Include a 'Use when...' clause with natural trigger phrases users would say (e.g., 'Use when the user mentions creating tickets, filing bugs, tracking tasks in Linear, or needs to add issues to their Linear workspace').
Remove the duplicate trigger term and expand with variations users might naturally use (e.g., 'linear ticket', 'create issue', 'file bug in linear', 'add to linear backlog').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Linear Issue Generator') without describing any concrete actions. There's no explanation of what the skill actually does - no verbs describing capabilities like 'creates issues', 'syncs data', or 'manages workflows'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are redundant ('linear issue generator, linear issue generator' - duplicated) and only match the exact skill name. Missing natural user phrases like 'create linear ticket', 'add issue to linear', 'linear task', or 'track in linear'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Linear' (a specific product) provides some distinctiveness from generic issue trackers, but 'Enterprise Workflows' is vague and could overlap with many other enterprise-focused skills. Without concrete actions, it's unclear what distinguishes this from other Linear-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no substantive content. It describes what a Linear issue generator skill would do without providing any actual implementation details, code examples, API references, or workflows. The content is entirely meta-description without actionable guidance.
Suggestions
Add executable code examples showing how to create Linear issues via API, including authentication and payload structure
Define a clear workflow: gather requirements → format issue data → call Linear API → validate response → handle errors
Include specific Linear API endpoints, required fields, and example JSON payloads for different issue types
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with concrete, Linear-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual Linear API usage or issue creation. The content only describes what the skill claims to do without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes documented for generating Linear issues. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no real information to disclose. There are no references to detailed documentation, API specs, or examples that would provide actual implementation guidance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.