CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-github-issue

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

Quality

94%

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

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

Excellent instruction-only skill body: copy-ready gh commands, a tightly sequenced workflow with human-in-the-loop validation and safety rules, and clean delegation of detail to one well-signaled external doc. No dimension shows a gap worth penalizing under the rubric.

DimensionReasoningScore

Conciseness

The ~36-line body is lean and assumes competence: no GitHub or gh concepts are explained, drafting detail is delegated to the external ticketing doc, and every sentence instructs — matching the 'every token earns its place' anchor with no padding to trim.

5 / 5

Actionability

Gives fully executable commands — `gh auth status`, `gh repo view --json nameWithOwner`, `gh issue create --title <title> --body-file <file> --assignee @me --label <label>`, `gh issue edit <n> --add-label <label>` — and covers the common cases: blockers ("Blocked by #<n>"), parking an issue without the label, and gh missing or not logged in.

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit checkpoints: an auth check with a recovery path ("ask the person to install it or run `gh auth login`, and wait"), a human approval gate before batch filing ("Show the drafts and wait for the person's yes"), blockers filed first so numbers exist, and refusal handling ("do not work around it: ask the person to run it"). The batch-operation validation cap does not apply since a validation gate is present.

5 / 5

Progressive Disclosure

A short, single-purpose skill with well-organized Steps and Rules sections and no bundle files to split; its single external reference (writing-factory-tickets.md) is one level deep and clearly signaled ("Read it first"), satisfying the simple-skill exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

87%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: concrete third-person capabilities, an explicit multi-scenario "Use when" clause, and a distinct Tessl-factory niche. The only shortfall is moderate keyword/synonym coverage and unmentioned skill features (labels, blockers), which keep specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

States concrete actions — "Write and file a GitHub issue", "turn into a pull request", "with the person's own GitHub account" — plus the split-into-ordered-issues scenario, but does not enumerate what the skill actually covers (label gating, blockers, gh mechanics), matching the 'several specific actions with minor gaps' anchor.

4 / 5

Completeness

Explicitly answers both "what" (write and file GitHub issues the factory converts to pull requests, filed as the person) and "when" via a "Use when" clause enumerating three concrete trigger scenarios, matching the top anchor rather than the merely-adequate level 4.

5 / 5

Trigger Term Quality

Natural user phrasings like "wants Tessl to work on something", "task split into issues", and "asks how to write an issue for Tessl" give good keyword coverage, though common synonyms such as "file an issue" or "ticket" are absent, fitting the 'good coverage, a few natural terms missing' anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Tessl factory issues in repositories "whose factory takes GitHub issues" — with Tessl-specific triggers that minimize overlap with generic issue-creation skills and distinguish it from the Linear sibling skill.

5 / 5

Total

18

/

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: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

boranfurkan/discordlancer

Path

.tessl/plugins/tessl/factory-setup/skills/create-github-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.