CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-lfg

Use when the user wants the GitNexus engineering pipeline run end-to-end on a task: gitnexus-plan (plan depth chosen up front), a blocking gate to execute with gitnexus-work or stop, finishing with a gitnexus-review of the result. Examples: "/gitnexus-lfg Add retry support to the ingestion pipeline", "run the gitnexus pipeline on this", "plan, build and review this feature".

76

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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-sequenced orchestrator that delegates logic to named sub-skills while supplying concrete decision rules for the gate, headless runs, and finding re-runs. Progressive disclosure is the lone near-miss only because the skill ships no bundle files to reference.

DimensionReasoningScore

Conciseness

Lean orchestrator prose that assumes Claude's competence and avoids explaining pipelines, PRs, or commits; every lane and policy (boundary triage, gate, headless handling, re-run limit) earns its tokens.

5 / 5

Actionability

Gives fully executable guidance — exact slash commands, numbered gate options, headless behavior, finding-routing bounds ('1–2 files, no architectural decisions'), and a bounded one-fix-cycle re-run policy — covering the common orchestration cases.

5 / 5

Workflow Clarity

Clear four-lane Plan→Gate→Work→Review sequence with an explicit blocking checkpoint, a headless fallback, and a structural-drift feedback loop (Deepen then return to the gate); the gate and bounded re-run serve as the validation checkpoints the destructive-ops cap looks for.

5 / 5

Progressive Disclosure

Well-organized into discrete lanes with no nested references and clean delegated pointers to the three sub-skills, but as a self-contained ~85-line file with no split-out bundle files to navigate to it falls just short of the one-level-deep references anchor 5.

4 / 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 high-quality description that crisply states both capability and trigger conditions with concrete natural-language examples. Trigger-term synonym breadth is the only minor weakness, keeping it just below a perfect score on that dimension.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions (gitnexus-plan, a blocking gate to execute with gitnexus-work or stop, finishing with gitnexus-review), giving comprehensive coverage for an orchestrator skill; the conventional third-person 'Use when the user wants…' trigger form avoids the second-person penalty.

5 / 5

Completeness

Explicitly answers both what (the three-lane plan→gate→work→review sequence) and when ('Use when the user wants the GitNexus engineering pipeline run end-to-end') with concrete example trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger phrases a user would say ('run the gitnexus pipeline on this', 'plan, build and review this feature') plus a slash-command example, but synonym breadth falls just short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (GitNexus pipeline orchestration) anchored by named sub-skills and a distinctive slash command, giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
abhigyanpatwari/GitNexus
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.