/log-provenance
Log derived files and trace provenance back to ENCODE source data
$ npx -y skills add ammawla/encode-toolkit --agent claude-codeShips with encode-toolkit. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/log-provenance
Context preview
What this command does when you run it.
Log derived files and trace provenance back to ENCODE source data
Command definition
log-provenance.mdname: log-provenance description: Log derived files and trace provenance back to ENCODE source data
Track provenance of files you create from ENCODE data.
Use `encode_log_derived_file` after creating derived files (filtered peaks, merged signals, differential analysis). Provide source accessions, tool used, and parameters. Use `encode_get_provenance` to trace any derived file back to its original ENCODE source.
Refer to the data-provenance skill for full provenance workflow guidance.
Search ENCODE, cross-reference 14 databases, run 7 analysis pipelines, and generate publication-ready methods — all from natural language in Claude Code.
Repo: ammawla/encode-toolkit
Other commands on encode-toolkit.
- /browse-files
List, search, and inspect ENCODE files by format, type, and assembly
Open command - /cite-encode
Generate ENCODE citations for publications, grants, and presentations
Open command - /compare-experiments
Check if two ENCODE experiments are compatible for combined analysis
Open command - /cross-reference
Cross-reference ENCODE data with PubMed, GEO, ClinicalTrials, and bioRxiv
Open command - /download-encode
Download ENCODE files (BED, FASTQ, BAM, bigWig) with MD5 verification
Open command - /manage-credentials
Store, check, or clear ENCODE API credentials for restricted data
Open command