r-rlang-programming
rlang metaprogramming for tidy evaluation and non-standard evaluation (NSE) in R. Use when building data-masking APIs, wrapping dplyr/ggplot2/tidyr functions with {{ !! !!! operators, implementing quosures and dynamic dots, or designing tidyverse-style DSLs—e.g., "tidy eval wrapper function", "embrace operator usage", "NSE programming patterns", "custom select helpers".
93
92%
Does it follow best practices?
Impact
92%
1.27xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive trigger terms that R programmers would naturally use, explicit 'Use when' guidance with multiple scenarios, and is highly distinctive within its technical niche. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'building data-masking APIs', 'wrapping dplyr/ggplot2/tidyr functions with {{ !! !!! operators', 'implementing quosures and dynamic dots', 'designing tidyverse-style DSLs'. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('rlang metaprogramming for tidy evaluation and NSE') and when ('Use when building data-masking APIs, wrapping dplyr/ggplot2/tidyr functions...'). Includes explicit 'Use when' clause with specific trigger scenarios and example phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'tidy eval', 'NSE', 'embrace operator', '{{ !! !!!' operators, 'quosures', 'dplyr', 'ggplot2', 'tidyr', 'tidyverse-style DSLs', 'custom select helpers'. These match how R programmers naturally describe these concepts. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting R's rlang/tidy evaluation specifically. The technical specificity ({{ !! !!! operators, quosures, data-masking APIs) makes it unlikely to conflict with general R skills or other programming skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill for rlang metaprogramming. It excels in actionability with executable code examples and progressive disclosure with clear references to detailed materials. The main weakness is some verbosity in conceptual explanations that Claude would already understand, though this is minor given the complexity of the topic.
Suggestions
Trim conceptual explanations like 'Code is data' and basic definitions of data masking - Claude knows these concepts
Consider moving the migration table to a reference file since it's supplementary information for users transitioning from base R
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory text that Claude would already know (e.g., 'Code is data' concept, basic explanations of what data masking is). The migration table and some conceptual framing could be trimmed, though most content is actionable. | 2 / 3 |
Actionability | Excellent executable code examples throughout - every pattern shows complete, copy-paste ready R code. The examples cover real use cases (wrapping dplyr, error handling, dynamic code construction) with specific function calls and expected outputs. | 3 / 3 |
Workflow Clarity | The decision tree provides clear sequencing for choosing the right approach. The 'Common Mistakes and Solutions' section shows explicit wrong/right patterns. Testing section includes validation steps. For a reference skill (not a multi-step process), the structure is appropriately clear. | 3 / 3 |
Progressive Disclosure | Excellent structure with a main overview containing essential patterns, then clear one-level-deep references to detailed files (references/tidy-evaluation.md, etc.). Each reference is clearly signaled with when to load it. The 'References (Load on Demand)' section explicitly guides navigation. | 3 / 3 |
Total | 11 / 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.
- Repository
- jjjermiah/dotagents
- Commit
b74de5e
- 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.