CtrlK
BlogDocsLog inGet started
Tessl Logo

github-author-context

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

62

Quality

73%

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

93%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 exemplary lean operational skill: concrete executable commands throughout, a clear prioritized source order with fallbacks, and a precise output template. Its only notable gap is the absence of explicit validation or error-recovery steps if a data source is missing or the API call fails. No bundle files exist, and none are needed at this size.

DimensionReasoningScore

Conciseness

The body is lean and fully instructional: no background explanations, every section is a command, condition, or output spec, and each token earns its place.

5 / 5

Actionability

Every step is copy-paste-ready — concrete `gh api`/`gh search` calls with jq projections, an `rg` fallback, git log/shortlog commands, and real invocations of the clawtributors helper with example flags.

5 / 5

Workflow Clarity

The numbered Source Order (1-4) is clearly sequenced with explicit fallback conditions and a skip rule for steipete, but there are no validation checkpoints or feedback loops (e.g., what to do when a lookup returns nothing), leaving a minor gap.

4 / 5

Progressive Disclosure

This is a compact, self-contained skill with well-organized sections (Inputs, Source Order, Output, Contributor Notes) and no external references needed; per the simple-skill exception, well-organized sections alone earn the top score.

5 / 5

Total

19

/

20

Passed

Description

53%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 concise and domain-specific, clearly signaling a GitHub contributor-profiling skill, but it reads as a topic label rather than a trigger. It lacks any "Use when..." guidance and misses natural trigger phrases like "PR author" or "review", which limits when-to-use discoverability. Adding an explicit trigger clause and concrete action verbs would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when reviewing PRs and you need author background, or when the user mentions a contributor's history, trust, or affiliation."

State concrete actions in third person rather than facets only, e.g., "Profiles a PR author: identity, merged/open PR activity, trust signal, company/team affiliation."

Include natural trigger synonyms such as "PR author", "contributor history", and "review" so users' phrasings match the description.

DimensionReasoningScore

Specificity

"GitHub contributor context" names the domain and "identity, activity, trust, company/team signal" enumerates several facets, but these are attributes rather than concrete actions, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is present ("identity, activity, trust, company/team signal") but there is no "when"/"Use when..." clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"GitHub contributor" and "trust" are relevant keywords, but common natural phrases a user would say are missing (e.g., "PR author", "review", "profile"), leaving partial keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"GitHub contributor context" carves a clear niche, but generic tokens like "identity", "activity", and "trust" create minor overlap risk with general PR-review or code-review skills.

4 / 5

Total

13

/

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