Menu
Capture non-obvious errors, data caveats, and performance gotchas discovered during analysis into repository memory for reuse.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Retrieve and use BERDL MinIO credentials and transfer result artifacts between BERDL object storage and the local machine. Use when exported query results need to be listed, downloaded, shared, or when only KBASE_AUTH_TOKEN is available and MinIO keys must be acquired.
Run SQL queries from a local machine against a provisioned BERDL Spark cluster using spark_connect_remote. Use when the user wants remote Spark compute with local control, needs clarity on connection and timeout behavior, or wants to return small/medium results directly before exporting large outputs.
Discover and document BERDL databases. Use when the user wants to explore a new database, generate documentation for a database, or create a module file for the berdl skill.
Query the KBase BERDL (BER Data Lakehouse) databases. Use when the user asks to explore pangenome data, query species information, get genome statistics, analyze gene clusters, access functional annotations, or query biochemistry data.
Search and review ecosystem and biogeochemical literature using MCP tools (PubMed, arXiv, bioRxiv, Google Scholar), with optional full-text reading and citation snowballing. Use when the user needs evidence, citations, methods comparison, or novelty checks for EcoSIM and warming-nitrogen hypotheses.
Review repository evidence and propose high-impact next research directions for EcoSIM, emphasizing warming-nitrogen mechanisms, data readiness, and methodological feasibility.
| name | pitfall-capture |
| description | Capture non-obvious errors, data caveats, and performance gotchas discovered during analysis into repository memory for reuse. |
| allowed-tools | Read, Write |
| user-invocable | true |
Use this skill when a task reveals a non-trivial pitfall that future work should not rediscover.
Default to repo memory:
/memories/repo/berdl-pitfalls.mdIf the file does not exist, create it.
## <short title>
- Date: YYYY-MM-DD
- Context: <task/skill>
- Symptom: <what failed or surprised>
- Cause: <root cause if known>
- Safe pattern: <what to do instead>
- Example: <optional command/query snippet>
Keep entries short, concrete, and reusable.