Base R error handling with tryCatch, withCallingHandlers, and custom condition classes. Use when implementing error recovery, debugging conditions, or working with stop/warning/message—e.g., "tryCatch in R", "custom condition class", "handle warnings and errors", "error recovery patterns".
Install with Tessl CLI
npx tessl i github:jjjermiah/dotagents --skill r-error-handling100
Does it follow best practices?
Validation 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 an excellent skill description that follows best practices. It uses third person voice, lists specific R functions and patterns, includes an explicit 'Use when...' clause with concrete trigger phrases, and is clearly distinguishable from other skills through R-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tryCatch', 'withCallingHandlers', 'custom condition classes', 'error recovery', 'debugging conditions', and 'stop/warning/message'. These are precise R language constructs and patterns. | 3 / 3 |
Completeness | Clearly answers both what (Base R error handling with specific functions and patterns) AND when (explicit 'Use when...' clause with multiple trigger scenarios like 'implementing error recovery', 'debugging conditions', plus example phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'tryCatch in R', 'custom condition class', 'handle warnings and errors', 'error recovery patterns'. Includes both function names and conceptual phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with R-specific terminology (tryCatch, withCallingHandlers, stop/warning/message) that clearly differentiates from generic error handling or other language error handling skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices across all dimensions. It's concise yet comprehensive, provides executable code for every pattern, includes clear decision guidance via the matrix and anti-patterns section, and properly structures advanced content into referenced files. The output contract checklist ensures verification before task completion.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with R. No unnecessary explanations of basic concepts—jumps straight to actionable patterns with minimal preamble. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Every pattern includes concrete implementation with proper function signatures, error classes, and usage examples. | 3 / 3 |
Workflow Clarity | Clear decision matrix for tool selection, explicit anti-patterns with consequences, and a verification checklist at the end. The 'Output Contract' section provides explicit validation checkpoints before completing tasks. | 3 / 3 |
Progressive Disclosure | Well-structured with quick reference up front, essential patterns in the middle, and clearly signaled one-level-deep references at the end for base R details, advanced rlang, and testing patterns. | 3 / 3 |
Total | 12 / 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.
Table of Contents
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.