r-error-handling
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".
99
100%
Does it follow best practices?
Impact
96%
1.95xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
90%
70%CSV Ingestion Validator
Custom error classes with rlang abort and call context
rlang::abort() used
0%
100%
Explicit namespacing
0%
100%
Class naming format
0%
100%
Specific error classes
0%
100%
call = caller_env()
0%
100%
caller_arg() for arg names
0%
100%
Bulleted message formatting
0%
100%
Package error helper
0%
0%
No silent error swallowing
100%
100%
No generic class in abort
100%
100%
98%
30%Multi-Layer Data Fetch Pipeline
Error chaining and recovery with try_fetch
try_fetch() used
0%
100%
Error chaining parent
100%
100%
Specific class per layer
100%
100%
Log before recovery
100%
100%
No silent swallow
100%
80%
call = caller_env() passed
100%
100%
Explicit rlang:: namespace
0%
100%
Class naming convention
50%
100%
Multi-layer chaining
100%
100%
try_fetch handler specificity
0%
100%
100%
40%Writing Tests for an Error Handling Module
Testing error conditions with testthat and rlang
expect_error with class
100%
100%
catch_cnd for metadata
0%
100%
snapshot testing
0%
100%
Parent chain assertion
100%
100%
Metadata field assertions
100%
100%
caller_arg name test
100%
100%
No class-less expect_error
100%
100%
Explicit rlang:: namespace in tests
0%
100%
Parametrized invalid inputs
0%
100%
No-error path tested
100%
100%
- Repository
- jjjermiah/dotagents
- Commit
b74de5e
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.