CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

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 gitnexus-lfg in abhigyanpatwari/GitNexus

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.

Excellent orchestrator body: lean, unambiguous lane sequencing with a blocking gate, explicit feedback loops, and precise delegation rules that avoid duplicating the underlying skills' logic. The only weakness is one dangling reference to a README that is neither pathed nor present in the bundle.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every paragraph encodes a non-inferable behavioral rule ("never inline a summary of what the skill would have done", "Never auto-proceed to execution") with no concept explanations or padding.

5 / 5

Actionability

Fully concrete instructions for an instruction-only skill: named skill invocations per lane, the exact fields of the gate summary, the blocking tool ("AskUserQuestion in Claude Code; a numbered list in chat on CLIs without a blocking tool"), headless-run behavior, and size-based routing rules for findings.

5 / 5

Workflow Clarity

Four clearly sequenced lanes with an explicit blocking validation checkpoint and feedback loops: structural drift routes back through a Deepen pass to the gate, and findings trigger one fix-and-re-review cycle with a stated stop condition.

5 / 5

Progressive Disclosure

A well-organized single-file overview that is appropriately structured for a thin orchestrator, but "Its re-evaluation governance lives in this skill's README" is an unsignaled external reference with no path and no corresponding bundle file, and the body exceeds the under-50-line simple-skill case.

4 / 5

Total

19

/

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: explicit trigger clause, concrete staged capability summary, and natural-language example invocations. Minor room to acknowledge non-pipeline paths or more trigger synonyms.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — "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" — but coverage has minor gaps (no hint of the boundary-triage or direct-mode alternatives).

4 / 5

Completeness

It explicitly answers both: the what (plan → gate → work → review, with each stage named) and the when ("Use when the user wants the GitNexus engineering pipeline run end-to-end on a task") with concrete trigger phrases in the examples.

5 / 5

Trigger Term Quality

Concrete example utterances like "run the gitnexus pipeline on this" and "plan, build and review this feature" give good natural-keyword coverage, though synonyms and common variations beyond the pipeline name are thin.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — the end-to-end pipeline request — that is distinct from the three skills it orchestrates (plan-only, work-only, review-only), so trigger conflict risk is minimal.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

abhigyanpatwari/GitNexus

Path

.claude/skills/gitnexus-lfg/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.