CtrlK
BlogDocsLog inGet started
Tessl Logo

github-author-context

GitHub contributor context: identity, activity, trust, company/team signal.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/github-author-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an exemplary lean, actionable instruction skill: every command is executable, the workflow is explicitly sequenced with decision checkpoints, and the structure is well-organized with no unnecessary reference indirection. No changes needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, providing only purpose, commands, and an output template with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

It gives fully executable gh/rg/git commands with jq filters and a copy-paste output block, leaving no ambiguity about what to run or produce.

3 / 3

Workflow Clarity

The Source Order (1-4) is clearly sequenced with explicit fallback logic and an upfront skip rule (steipete); as a read-only gather-and-summarize task it needs no destructive-operation validation loop, satisfying the simple-skill allowance.

3 / 3

Progressive Disclosure

This is a self-contained single-purpose skill well under 50 lines with no bundle files and no external references, organized into clear sections (Inputs, Source Order, Output, Contributor Notes), qualifying for the top anchor under the simple-skill guideline.

3 / 3

Total

12

/

12

Passed

Description

57%

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 clearly scopes a specific GitHub contributor-context niche but reads as a domain/facet list rather than a list of concrete actions and lacks any explicit 'when to use' trigger. Adding a verb-led action clause and a 'Use when reviewing PRs...' trigger would lift specificity and completeness.

Suggestions

Lead with concrete actions, e.g. 'Builds a compact maintainer-facing profile of a PR author: identity, activity, trust signals, and company/team affiliation.'

Add an explicit trigger clause such as 'Use when reviewing PRs or when the user asks about a GitHub contributor's background or trustworthiness.'

Include natural trigger terms users would say ('PR author', 'author profile', 'contributor trust') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and several facets ('identity, activity, trust, company/team signal') but lists what is gathered rather than concrete actions/verbs, so it does not reach the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It clearly answers 'what' (contributor context facets) but provides no 'Use when...' or equivalent explicit trigger guidance in the description, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

'GitHub contributor context' is a relevant natural term, but common variations a user would say ('PR author', 'author profile', 'PR review') are missing, so coverage is partial rather than complete.

2 / 3

Distinctiveness Conflict Risk

The description targets a clear niche (GitHub contributor context) with distinct framing that is unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

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
steipete/agent-scripts
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.