roman-space-telescope
Skill0 starsChanged 6 months agoNo licenceView on GitHub
Nancy Grace Roman Space Telescope skill for Emmanuel at IPAC Caltech. Apply whenever a task involves Roman mission data products, the WFI instrument, ASDF pipeline outputs, the SOC file exchange system, romancal pipeline operations, romanisim/STPSF/Pandeia/STIPS simulations, Roman IRSA/MAST data access, ObsCore queries for Roman observations, EKS deployment of Roman SOC services, Roman science planning (HLWAS, HLTDS, GBTDS, GPS surveys), roman_photoz, rad (Roman Attribute Dictionary), PySIAF aperture files, or Roman Research Nexus workflows. Trigger for: "roman", "roman wfi", "roman soc", "roman pipeline", "romancal", "romanisim", "roman asdf", "roman file exchange", "wfi filter", "roman survey", "roman calibration", "level 2 roman", "pandeia roman", "stpsf roman", "stips roman", "roman_photoz", "rad roman", "roman nexus", "roman notebooks". Do NOT trigger for generic ASDF/FITS questions unrelated to Roman.
- Installs packages
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-orchestrationSkill
- ai-agent-md-architectSkill
- astropySkill
- changelog-generatorSkill
- codebase-onboardingSkill
- context7-docs-lookupSkill
- data-toolsSkill
- emmanuel-engineeringSkill
- git-workflowSkill
- lsdbSkill
- emmanuel-markdownSkill
- mcp-builderSkill
- paper-lookupSkill
- polarsSkill
- prompt-auditSkill
- qaSkill
- readme-driven-devSkill
- scientific-visualizationSkill
- senior-prompt-engineerSkill
- senior-qaSkill
- statistical-analysisSkill
- tddSkill
- think-firstSkill
- vo-explorerSkill
- zarr-pythonSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.