CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-linear-issue

Write and file a Linear issue for the Tessl factory to turn into a pull request, with the person's own Linear access, and delegate it to Tessl. Use when someone wants Tessl to work on something in a repository whose factory takes Linear issues, wants a task split into issues the factory builds in order, or asks how to write an issue for Tessl.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tessl/factory-setup

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A tight, well-structured procedural skill: an explicit 8-step workflow with genuine human-in-the-loop checkpoints (draft approval before filing, ask-and-wait on ambiguity), lean prose that assumes competence, and clean one-level-deep references to the ticket-writing doc and sibling skills. The only gap is that issue-creation mechanics and draft format live entirely in the referenced doc, leaving minor executable detail out of the body. No bundle files (references/, scripts/, assets/) exist in this skill to further disclose.

DimensionReasoningScore

Conciseness

The ~48-line body is lean: terse numbered steps and rules with zero concept explanations, no padding, and no background Claude already knows (e.g. it never explains what Linear or an issue tracker is). Every token carries instruction — matching anchor 5's 'every token earns its place' rather than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Mostly executable guidance: a copy-paste-ready lookup command ("tessl api /v1/orgs/<org id>/integrations/linear/routes"), the exact env var (LINEAR_API_KEY), concrete state names (Todo, Backlog), per-case filing branches (no blockers / with blockers / park), and stop-work instructions. Minor gaps remain — the actual issue-creation call syntax and a sample issue draft are not shown, only delegated to the referenced ticket-writing doc — so it sits at anchor 4 ('minor gaps') rather than anchor 5's fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with explicit checkpoints and feedback loops: "Show the drafts and wait for the person's yes" before any batch write, "With neither, ask the person... and wait", "When more than one team fits, ask which", and error recovery in the rules ("When a call is refused, do not work around it: ask the person"). Because a validation checkpoint exists before filing, the batch-operation cap does not apply, and the content matches anchor 5.

5 / 5

Progressive Disclosure

The body is a well-organized overview (Steps, Rules) with clearly signaled, one-level-deep references — [Writing a ticket for the factory](../../docs/writing-factory-tickets.md), [Regional setup](../factory-setup/references/region.md), and the create-github-issue skill link — and no bundle files of its own to inline. This matches anchor 5's clean overview-plus-clear-references pattern; there is no nesting, burying, or inlined bulk content that would justify anchor 4.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong description: it names the concrete actions (write, file, delegate, use the person's own access), uses third person, and includes an explicit multi-clause 'Use when' trigger set with natural phrasing. Its only weakness is modest synonym coverage of trigger terms. It avoids over-claims and stays concise while remaining complete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Write and file a Linear issue for the Tessl factory to turn into a pull request", "with the person's own Linear access", "delegate it to Tessl" — covering the skill's function comprehensively with no vague filler. Anchor 4 ('minor gaps in coverage') doesn't fit since every core capability of the skill is named.

5 / 5

Completeness

Explicitly answers both: what ("Write and file a Linear issue... and delegate it to Tessl") and when ("Use when someone wants Tessl to work on something in a repository whose factory takes Linear issues, wants a task split into issues..., or asks how to write an issue for Tessl") with concrete trigger phrases. This mirrors the anchor-5 example's structure; anchor 4's 'when could be more explicit' criticism doesn't apply.

5 / 5

Trigger Term Quality

The "Use when" clause gives natural phrasings users would say — "wants Tessl to work on something", "wants a task split into issues the factory builds in order", "asks how to write an issue for Tessl" — plus strong domain terms (Linear issue, Tessl, pull request). A few natural variants like "create a ticket" or "file an issue in Linear" are absent, so it sits at good-but-not-comprehensive coverage (anchor 4) rather than anchor 5's full synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The Tessl-factory / Linear-issue / delegate-to-Tessl niche is highly specific and would not plausibly trigger any other skill; the trigger conditions are tightly scoped to repositories whose factory takes Linear issues. Clear niche with distinct triggers, matching anchor 5; no overlap risk that anchor 4's 'minor overlap' would describe.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

boranfurkan/discordlancer

Path

.tessl/plugins/tessl/factory-setup/skills/create-linear-issue/SKILL.md

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.