init-workspace-rules
Rosetta skill to create local cached agent rules configured for IDE/OS/project context.
37
35%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./instructions/r2/core/skills/init-workspace-rules/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague and jargon-heavy to be effective for skill selection. It lacks concrete actions, natural trigger terms, and any explicit guidance on when Claude should use this skill. The only slight positive is the 'Rosetta' branding which provides some distinctiveness.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to set up agent rules, configure project-specific settings, or initialize cached configurations for their IDE.'
Replace jargon with natural language and list specific actions, e.g., 'Creates and caches local agent configuration rules based on the user's IDE, operating system, and project type. Generates .rules files, detects project context, and applies OS-specific defaults.'
Include natural trigger terms users might say, such as 'agent config', 'project rules', 'setup rules', 'configure agent', '.rules file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'local cached agent rules' and 'configured for IDE/OS/project context' without listing concrete actions. It doesn't specify what actions are performed beyond 'create'. | 1 / 3 |
Completeness | The description weakly addresses 'what' (create cached agent rules) but provides no 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent. | 1 / 3 |
Trigger Term Quality | The terms 'Rosetta', 'cached agent rules', and 'IDE/OS/project context' are technical jargon that users would not naturally say. A user would more likely say something like 'set up rules', 'configure agent', or 'project settings'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Rosetta' and 'cached agent rules' is somewhat distinctive and unlikely to overlap with many other skills, but the vague framing around 'IDE/OS/project context' could still cause confusion with other configuration or setup skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured workflow for creating local cached agent rules with clear sequencing and validation steps. Its main weaknesses are the lack of concrete examples (no sample file outputs, path mappings, or frontmatter formats) and the absence of supporting bundle files that would make the instructions more actionable. The workflow clarity is strong with explicit verification checkpoints and HITL confirmation.
Suggestions
Add a concrete example showing a sample ACQUIRE output and the resulting local file with IDE-specific frontmatter adaptation, so the adaptation process is unambiguous.
Include an example of the exclusion set filtering — show a sample LIST output and which items get excluded and why.
Provide a sample directory structure showing expected output for at least one IDE configuration to make the file mapping concrete.
Consider extracting the configure file format specifications into a referenced bundle file to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary framing (role tag, when_to_use_skill explanation) and could be tightened. The core_concepts section has useful constraints but some items are somewhat redundant with the process steps. | 2 / 3 |
Actionability | The skill provides a clear multi-step process with specific commands (LIST, ACQUIRE) and concrete file references (rules/local-files-mode.md, rules/bootstrap-*.md), but lacks executable code examples, concrete file path mappings, or example outputs. The instructions rely heavily on external KB resources and configure files without showing what those look like. | 2 / 3 |
Workflow Clarity | The 6-step process is clearly sequenced with explicit validation checkpoints in Step 6 (count verification, no absolute paths, version marker check, bundled content merge verification). There's a feedback loop via HITL confirmation, upgrade mode handles skip logic, and the validation checklist provides final verification criteria. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with distinct sections (core_concepts, process, validation_checklist, pitfalls), but everything is in a single monolithic file with no references to supporting documentation. Given the complexity of multi-IDE configuration, external references for configure specs or examples would improve navigation. No bundle files are provided to support the content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- griddynamics/rosetta
- Commit
ade2cc5
- 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.