r-expert
Core R programming skill for all R code, package development, and data science workflows. Use when writing R functions, building packages, using tidyverse (dplyr, ggplot2, purrr), creating Shiny apps, working with R Markdown/Quarto, or doing data analysis—e.g., "write an R function", "refactor this R code", "create a Shiny dashboard", "set up package tests", "debug R errors".
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is a strong skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche for R programming that won't conflict with other language-specific skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'writing R functions', 'building packages', 'using tidyverse (dplyr, ggplot2, purrr)', 'creating Shiny apps', 'working with R Markdown/Quarto', 'data analysis'. The parenthetical examples add further specificity. | 3 / 3 |
Completeness | Clearly answers both what ('Core R programming skill for all R code, package development, and data science workflows') and when ('Use when writing R functions, building packages...') with explicit 'Use when' clause and concrete example triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'R function', 'R code', 'tidyverse', 'dplyr', 'ggplot2', 'purrr', 'Shiny', 'R Markdown', 'Quarto', 'package tests', 'debug R errors'. The quoted examples ('write an R function', 'create a Shiny dashboard') mirror actual user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on R programming with distinct triggers like 'R function', 'Shiny', 'tidyverse', 'R Markdown'. These are R-specific terms unlikely to conflict with Python, JavaScript, or general data skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable R guidance with executable code examples and good progressive disclosure through complementary skills. However, it suffers from repetitive emphatic language ('No exceptions', 'Every time') that inflates token count without adding value, and the workflow lacks explicit validation checkpoints for error recovery in multi-step processes.
Suggestions
Remove repetitive warning phrases ('No exceptions', 'Every time', 'NEVER skip') - Claude understands emphasis from a single clear statement
Add validation checkpoints to the Core Workflow, e.g., 'Run devtools::check() after step 3, fix any issues before proceeding'
Consolidate the multiple Context7 reminders into a single, prominent callout rather than repeating throughout
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary repetition ('No exceptions', 'Every time') and over-explains the importance of Context7 multiple times. The core content is useful but could be tightened by removing redundant warnings. | 2 / 3 |
Actionability | Provides fully executable code examples for data pipelines, file operations, and clear package structure. The code is copy-paste ready with proper package::function() notation and realistic patterns. | 3 / 3 |
Workflow Clarity | The 4-step core workflow is listed but lacks validation checkpoints. For package development or data pipelines, there's no explicit verify/fix/retry loop. The sequence is present but missing feedback mechanisms for error recovery. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of complementary skill references, and a single-level-deep reference to r-context7-mappings.md. Content is appropriately split between overview and detailed references. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.