CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-add-contributor

Add or reconcile flutter_rust_bridge contributors through all-contributors PRs. Use when finding contributor PRs, posting all-contributors comments, validating contributor metadata, resolving contributor PR merge conflicts, or merging the generated contributor PRs.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable workflow with strong validation checkpoints and feedback loops appropriate to its batch/PR-merging nature. Slight conciseness gains are available by de-duplicating the mandatory-stop constraint lists.

Suggestions

Consolidate the overlapping 'Do not...' prohibition lists in Steps 2 and 3 into a single shared constraint block to reduce repetition and token cost.

Fix the self-referential wording in Step 3 ('Do not continue to Step 3 or any later step in this skill') since the reader is already in Step 3 — rephrase to 'Do not proceed to Step 4 or any later step'.

Consider extracting the conflict-resolution sub-procedure (Step 7) into a reference file if the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Mostly lean with concrete commands and no concept over-explanation, but the mandatory-stop constraint lists in Steps 2 and 3 overlap somewhat and the phrasing 'Do not continue to Step 3' from within Step 3 adds minor repetition.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (gh search prs, gh pr comment, ./frb_internal generate-internal-contributor, gh pr checkout, git merge, gh pr merge, gh pr list) with clearly marked placeholders covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 9-step process with explicit mandatory human-confirmation checkpoints (Steps 2 and 3), a metadata validation step (Step 5), a conflict-resolution workflow (Step 7), a retry-on-DIRTY feedback loop (Step 8), and a final verification checklist (Step 9).

5 / 5

Progressive Disclosure

Well-organized into nine clearly headed sections with no nested references, but at ~170 self-contained lines with no external reference files, structure is good rather than optimally split; nothing here demands separation, yet the length slightly exceeds the simple-skill ideal.

4 / 5

Total

18

/

20

Passed

Description

92%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, specific description that clearly states both the skill's purpose and its trigger conditions with concrete, enumerated use cases. Minor room for improvement in natural-synonym coverage of trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add or reconcile', 'finding contributor PRs', 'posting all-contributors comments', 'validating contributor metadata', 'resolving contributor PR merge conflicts', 'merging the generated contributor PRs' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' ('Add or reconcile flutter_rust_bridge contributors through all-contributors PRs') and 'when' ('Use when finding contributor PRs, posting all-contributors comments...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause enumerates natural trigger phrases a user would say (finding contributor PRs, posting all-contributors comments, resolving merge conflicts), but a few natural synonyms like 'credit' or 'acknowledge contributors' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a very specific niche — flutter_rust_bridge all-contributors management — with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fzyzcjy/flutter_rust_bridge
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.