CtrlK
BlogDocsLog inGet started
Tessl Logo

update-stars

Update Remotion homepage GitHub star counts. Use when asked to refresh the displayed GitHub star count and push the change to main.

63

Quality

73%

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/update-stars/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is impressively lean and well-organized for a simple task, with explicit file targets and a precise rounding rule. It falls short on actionability (no fetch command or edit specifics) and workflow clarity (no validation before the irreversible push to main).

Suggestions

Add a concrete command to fetch the star count (e.g., a `gh` API call) and specify what values to update inside CommunityStatsItems.tsx and GitHubButton.tsx so the guidance is copy-paste ready.

Insert a validation checkpoint before pushing, such as confirming the rounded count is correct and the repo builds/tests pass, since 'push to main' is an irreversible batch/destructive operation.

Clarify the rounding verification step (e.g., show the integer math or an example) so the 'round down to the closest 1000' rule cannot be misapplied.

DimensionReasoningScore

Conciseness

Every line earns its place with no padding or explanation of concepts Claude already knows ('Check on GitHub how many stars Remotion has', 'Always round down to the closest 1000, never round up'), matching the lean level-3 anchor.

3 / 3

Actionability

Provides concrete file paths and a clear rounding rule, but gives no executable command to fetch the star count and does not specify what to change inside the two files, so key execution details are missing per the level-2 anchor.

2 / 3

Workflow Clarity

The sequence (check stars, round down, update two files, commit and push) is clear, but pushing to main is an irreversible step with no validation checkpoint or feedback loop, which caps workflow clarity at 2 per the destructive-operation guideline.

2 / 3

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no external references needed, and the body is cleanly organized into discrete points, so it qualifies for the level-3 simple-skills allowance.

3 / 3

Total

10

/

12

Passed

Description

75%

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 clearly answers both what the skill does and when to use it, with a distinctive niche and explicit trigger. Its main weakness is narrow trigger-term coverage and only a single concrete action rather than multiple.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Update Remotion homepage GitHub star counts', 'push the change to main') but it is a single narrow task rather than multiple distinct concrete actions, so it does not reach the level-3 anchor.

2 / 3

Completeness

Clearly answers what ('Update Remotion homepage GitHub star counts') and when via an explicit 'Use when...' trigger clause, matching the level-3 anchor exactly.

3 / 3

Trigger Term Quality

Uses some natural trigger terms ('refresh the displayed GitHub star count', 'push the change to main'), but coverage is thin with no common variations like 'update stars' or 'star count', matching the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

Targets a very specific niche (Remotion homepage GitHub star counts) with distinct triggers, making it unlikely to conflict with other skills; matches the level-3 anchor.

3 / 3

Total

10

/

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
remotion-dev/remotion
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.