vimalinx/bio-agent / .claude/skills/popt
popt
UnverifiedUse when filtering `RNAsubopt -s` output to keep p-optimal RNA structures in a ViennaRNA post-processing pipeline.
popt
Quick Start
- Command:
RNAsubopt -s < seq.fa | popt - Local executable:
/home/vimalinx/miniforge3/envs/bio/bin/popt - Observed usage string:
p-optimal filter to subopt output. usage: RNAsubopt -s < seq | popt
When To Use This Tool
- Filter an
RNAsuboptstructure ensemble down to p-optimal structures. - Keep the workflow inside ViennaRNA-style shell pipelines.
- Post-process suboptimal RNA secondary structures without writing custom selection code.
Common Patterns
# 1) Directly filter RNAsubopt output
RNAsubopt -s < sequences.fa | popt
# 2) Keep the raw ensemble and the filtered subset
RNAsubopt -s < sequences.fa | tee all_subopt.txt | popt > p_optimal.txt
Recommended Workflow
- Generate compatible input with
RNAsubopt -s. - Pipe that output directly into
popt. - Save the filtered subset separately if you will compare it against the full suboptimal ensemble.
- Continue with downstream ViennaRNA analysis only after confirming the filtered output still matches your expected sequence set.
Guardrails
poptis a stdin filter; it is not a standalone predictor.- The live binary does not expose a clean
-h/--helpinterface in this environment, so the usable contract comes from the embedded usage string and ViennaRNA context. - The intended input format is specifically
RNAsubopt -soutput, not arbitrary dot-bracket text. - Current documentation here is grounded in the binary usage string and surrounding ViennaRNA conventions, because the local executable is an ELF binary rather than a short inspectable script.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |