CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

repository-routing-security

Use when changing fork routing, forge-profile identity, provider-plugin host selection, repository URL persistence, credential redaction, the repo-config trust boundary (trusted-default-branch-only fields), gate-agent instruction neutralization, or repository-declared extra gates.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/repository-routing-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an exceptionally concrete, well-sourced set of security invariants with exact file/function/test anchors — highly actionable for its genre. Its weaknesses are token efficiency and structure: enormous run-on bullets with historical rationale, and monolithic single-file density where per-area reference files would ease navigation.

Suggestions

Split each major area (Fork Routing, Forge Identity, Redaction, Trust Boundary, Gate Neutralization, Extra Gates) into its own reference file under references/ and keep SKILL.md as a short overview of the invariants, which would address both progressive disclosure and token load.

Break the mega-bullets into short imperative lines (invariant → anchor file/function → regression tests) and trim historical narrative such as issue/PR triage backstory and tool version notes to a compact 'history' note per section.

Add a short per-area checklist (make the change → run the named regression tests → confirm fail-closed behavior) so the implicit validation checkpoints become an explicit workflow.

DimensionReasoningScore

Conciseness

The body contains no beginner-concept padding and every fact is project-specific, but single bullets run ten or more lines and embed historical narrative ("per the maintainer's triage on #1178", "Greptile finding on PR #1183", "empirically verified against omp 18.2.0") that is not needed to apply the invariant. This fits anchor 3 (mostly efficient but could be tightened) better than anchor 4, which expects only minor trims.

3 / 5

Actionability

Directives are imperative and anchored to exact symbols, files, and flags ("resolve the push URL via `resolvePushURL` (`internal/pipeline/steps/common_git.go`)", "Reuse `internal/safeurl` for new redaction sites rather than adding a git-local helper", "never pass `<owner>:<branch>` to `gh pr list --head`"), with named regression tests per area. For an instruction-only skill this is fully concrete guidance covering the common cases, matching anchor 5; the rubric notes say absence of code is not penalized when guidance is actionable.

5 / 5

Workflow Clarity

The content is organized by subsystem rather than as a sequenced process — there are no ordered steps and no explicit validate→fix→retry loops; the extensive regression-test lists serve only as implicit checkpoints. This matches anchor 3 (checkpoints missing or implicit); it is a multi-area invariants skill, so the simple-skill exception to score 5 does not apply, and no destructive/batch cap is triggered.

3 / 5

Progressive Disclosure

Six clearly bold-headed sections give real structure, but roughly 20 KB of dense invariants live in one file with no bundle files — the repo-config trust boundary section alone is a wall of text that clearly belongs in a separate reference. This fits anchor 3 (some structure, but content that should be separate is inline) rather than anchor 4's appropriately split layout.

3 / 5

Total

14

/

20

Passed

Description

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

The description is a precise, low-conflict trigger list for an internal routing/security skill, with excellent domain-specific trigger terms. Its main weakness is that it never states what the skill actually does, leaving the capability half of the description implicit.

Suggestions

State the 'what' explicitly, e.g. 'Apply the routing, redaction, and trust-boundary invariants (with named regression tests) when changing fork routing, forge-profile identity, ...' so the description answers both what the skill provides and when to use it.

Add a few natural synonyms or adjacent phrasings users might say, such as 'push/upstream URL handling', 'gh auth or glab profile selection', or 'custom repo gates', to broaden trigger coverage.

Consider trimming the parenthetical '(trusted-default-branch-only fields)' or folding it into the trigger phrase so the enumeration reads more naturally.

DimensionReasoningScore

Specificity

The description enumerates eight concrete change-areas ("fork routing, forge-profile identity, provider-plugin host selection, repository URL persistence, credential redaction, the repo-config trust boundary ... gate-agent instruction neutralization, or repository-declared extra gates") with no vague language. It falls short of anchor 5 because these are trigger topics rather than explicitly stated capabilities or actions the skill performs.

4 / 5

Completeness

The "when" is explicit and strong ("Use when changing ..."), but the "what" is never stated — the skill's actual function (providing invariants, contracts, and regression guidance) is only implied by the enumeration. This mirrors anchor 3 (one half clear, the other only weakly implied) rather than anchor 4, which requires both explicitly present.

3 / 5

Trigger Term Quality

Phrases like "fork routing", "credential redaction", "trust boundary", and "gate-agent instruction neutralization" are the natural terms a developer of this codebase would use when touching these areas. Not anchor 5 because each term appears once with no synonyms or variations (e.g. "push URL", "upstream", "extra gates config") that users might equally say.

4 / 5

Distinctiveness Conflict Risk

Highly niche internal topics such as "forge-profile identity", "trusted-default-branch-only fields", and "repository-declared extra gates" carve out a clear, distinctive trigger space with minimal overlap risk against any other skill. This matches anchor 5 (clear niche with distinct triggers).

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/repository-routing-security/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.