reporting-metadata-columns
Skill10 starsChanged 45 days agoNo licenceView on GitHub
Use when documenting, describing, auditing or presenting the metadata columns of a Seurat object (or SingleCellExperiment, AnnData obs, or any per-cell table) as a reference report. Triggers include "list the metadata columns", "describe the columns in the object", "update the metadata summary", "which columns did I add vs the provider", "make a column dictionary / data dictionary / codebook for the Seurat object", a collaborator or core facility delivering a metadata report (e.g. a `Metadata_Summary.md` or Rmd with coloured category pills) that needs extending with the analyst's own columns, or checking that every column in a checkpoint is documented. Produces a lettered Quarto notebook outside the numbered pipeline that detects columns programmatically from each object, splits them into provider vs analyst columns, assigns a category and data type, renders colour-coded HTML cards with live summaries, groups families of score columns (AddModuleScore, ssGSEA, CoRAL), writes a registry CSV, and flags undocumented, missing and pending columns. Use even when the user only asks for "an updated list of columns" or "a table of what each column means".
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-report-styleSkill
- creating-analysis-projectsSkill
- developing-r-packagesSkill
- git-hygieneSkill
- hugo-blogSkill
- md-formatSkill
- md-to-htmlSkill
- naming-conventionsSkill
- qmd-runnerSkill
- recommendation-letter-workflowSkill
- resource-watched-runSkill
- tailoring-applicationsSkill
- write-readmeSkill
- writing-labarchive-entriesSkill
- writing-qmd-scientificSkill
- writing-r-codeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
8
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.