All authors
Claude Skills by fdiblen
github.com/fdiblen68 skills0 installs65 views
- Rseng Reproducible EnvironmentsCovers making research software environments reproducible: pinning a language version and its dependencies in a per-project virtual environment, choosing a package/environment manager, and packaging code and its full stack into a container. Use when the user asks how to set up venv/conda/poetry/uv/renv, lock or pin dependencies, share a runnable environment, escape "dependency hell" or "works on my machine", write a Dockerfile, build an Apptainer/Singularity image for HPC, or decide between a...Votes: 0GitHub stars: 20
- Rseng Research IntegrityCovers integrity checks on research outputs before submission or release: statcheck/GRIM-style consistency of reported statistics, agreement between manuscript numbers and pipeline outputs, retraction screening of cited work, sanity checks on tables and figures against the data, and an auditable pre-submission checklist. Use PROACTIVELY before manuscript submission or release of result-bearing reports, when reported numbers are transcribed from analysis outputs, and when the user asks to chec...Votes: 0GitHub stars: 20
- Rseng Science CommunicationCovers communicating research software outward to research audiences: supporting the user's software papers (JOSS/SoftwareX-style) with outlines, gathered material and structure - never writing a submission-ready manuscript - plus release announcements, lay summaries of what the software does, talk and poster outlines, blog posts, and making a package findable to its intended users. Use when the user wants to announce, present, promote or explain their research software, asks for help with a ...Votes: 0GitHub stars: 20
- Rseng Scientific File FormatsCovers choosing and handling scientific data formats in code: HDF5 and NetCDF for array data, CF conventions and standard metadata, Parquet for tabular data, domain standards (NeXus and similar), self-describing files, chunking and compression choices, and migrating away from fragile formats like pickles and ad-hoc binaries. Use when the user chooses a file format for research data, reads or writes HDF5/NetCDF/Parquet/zarr-style stores, asks about chunking, compression or metadata embedding, ...Votes: 0GitHub stars: 20
- Rseng Scientific VisualizationCovers visualization of scientific data beyond publication figures: 3D and volumetric rendering with ParaView and VTK, scripted and reproducible visualization pipelines, state files and Python trace for repeatability, in-situ visualization of running simulations, web-delivered interactive 3D (trame-style apps), and choosing honest colormaps and representations for spatial data. Use when the user works with 3D, volumetric, mesh or simulation output data, mentions ParaView, VTK or interactive 3...Votes: 0GitHub stars: 20
- Rseng SecurityCovers securing research software and its supply chain: secrets and sensitive-file hygiene (env files, keys, credentials and the never-commit file catalog) with leak response, dependency vulnerability scanning and pinning, OpenSSF Scorecard and Best Practices badge, SLSA provenance levels, SBOMs, signed releases and repository hardening. Use PROACTIVELY when setting up CI or releases, when an API key, password, credential or token is committed or appears in code or history, when the user asks...Votes: 0GitHub stars: 20
- Rseng Software DesignCovers designing research software: modularity and separation of concerns, interfaces and coupling, growing from script to package, the rule of three and the reuse ladder, architecture styles for research systems (pipeline, layered, plugin, services), quality-attribute trade-offs, visual design documentation (C4, Mermaid, PlantUML diagrams-as-code) and architecture decision records. Use when starting non-trivial research software, when a script has grown past easy understanding, when the user...Votes: 0GitHub stars: 20
- Rseng Software MetricsCovers measuring code health quantitatively: cyclomatic complexity, code duplication, coupling and cohesion, code churn, maintainability index, size conventions and documentation coverage - running radon, lizard, jscpd, interrogate and SonarQube-class tools, interpreting numbers against community conventions and the software's tier, wiring metric gates into CI, and avoiding metric gaming. Use when the user asks how healthy, complex or maintainable their code is, wants metrics or duplication m...Votes: 0GitHub stars: 20
- Rseng Software Peer ReviewCovers community peer review of research software: preparing a package for JOSS, pyOpenSci or rOpenSci submission, self-checking against their review criteria before submitting, writing the paper or statement of need, responding to reviews, and acting as a reviewer or CODECHECK-style codechecker who executes the artifact. Use when the user mentions JOSS, pyOpenSci, rOpenSci or CODECHECK, wants to submit software for peer review or publication, asks whether their package is review-ready, or is...Votes: 0GitHub stars: 20
- Rseng Software PublishingCovers publishing research software through its distribution channels: packaging for and releasing on package indexes (PyPI, conda-forge, CRAN and ecosystem equivalents), registering in research software registries, submitting to software journals (JOSS-style), and choosing the channel mix for a project's audience. Use when the user wants their software installable by others, asks how to publish on PyPI, CRAN or conda-forge, wants the software listed where researchers search, or when a mature...Votes: 0GitHub stars: 20
- Rseng Software ReuseCovers discovering and reusing existing research software instead of rebuilding it, using Research Software Directory (RSD) instances such as research-software-directory.org and helmholtz.software. Use PROACTIVELY when a research project is about to implement functionality that likely already exists - data readers, converters, solvers, analysis tools, domain libraries - and when the user asks whether a tool already exists, wants to find research software for a domain, or mentions the RSD. Shi...Votes: 0GitHub stars: 20
- Rseng StorytellingCovers telling the story of research data, software and projects to broad audiences: narrative structure for data stories, turning milestones into human-centered stories, and citizen-science engagement - recruiting contributors, closing the feedback loop with data stories, honest narrative that never oversells. Use when the user wants to explain a project, dataset or tool to non-specialists, mentions storytelling, outreach, public engagement or citizen science, or needs project stories for we...Votes: 0GitHub stars: 20
- Rseng TestingCovers how to test research software: choosing test types and levels (unit, integration, system, regression, property-based, golden-master), test frameworks and coverage, TDD, validating analysis code against reference cases, and taming CI testing matrices across compilers, platforms and dependency versions. Use when the user asks how to write tests, set up pytest/testthat/JUnit, decide what to test, raise or interpret code coverage, do test-driven development, or when a CI matrix is explodin...Votes: 0GitHub stars: 20
- Rseng TrainerCovers teaching research software skills while working: turning everyday coding moments into short, learner-centered lessons using Carpentries/CodeRefinery-style pedagogy (objective-led episodes, formative checks, error normalization), and routing learners to canonical training materials. Use when a teachable moment appears during a task (offer a one-line lesson, never lecture), when the user asks to learn a topic, requests an explanation or tutorial, wants training material recommendations, ...Votes: 0GitHub stars: 20
- Rseng User SupportCovers running user support as an operation for research software: triaging and answering support requests, converting recurring questions into documentation and FAQ entries, office hours and support channels, forum gardening, and feeding support signals into the roadmap. Use when support questions arrive faster than they are answered, when the same question keeps being answered by hand, when the user asks how to organize support, office hours or a helpdesk for their software, or when support...Votes: 0GitHub stars: 20
- Rseng Ux AccessibilityCovers user experience and accessibility for research software: UX disciplines, accessibility practice, Design Thinking, scoping a Minimum Viable Product versus a Minimum Loveable Product, Nielsen's usability heuristics, and prototyping with tools like Figma and Miro. Also covers WCAG conformance for web-facing tools, accessibility testing, CLI usability guidelines and inclusive defaults. Use PROACTIVELY when creating or reshaping a user-facing interface (CLI, GUI, web), and when the user des...Votes: 0GitHub stars: 20
- Rseng Version Control ReviewCovers using version control effectively for research software and the PR-time review process: choosing a VCS, branching and commit practice, authorship and signatures in commit metadata (author/committer identity, Co-authored-by trailers, signed commits and tags, .mailmap), collaboration on GitHub/GitLab, and constructive checklist-driven pull-request reviews. Use when the user asks how to set up git, design a branching strategy, write commit messages, record who authored or co-authored a ch...Votes: 0GitHub stars: 20
- Rseng WorkflowsCovers building, choosing, discovering, describing, and sharing computational workflows with workflow management systems - when to move off ad-hoc scripts onto a WMS, how to make workflows FAIR, and where to find or register them. Use when the user asks how to automate a multi-step data pipeline, mentions Snakemake, Nextflow, CWL, WDL, Galaxy, Apache Airflow, Parsl, nf-core, or WorkflowHub, wants to pick a workflow engine, package a workflow with RO-Crate metadata, or make an analysis pipelin...Votes: 0GitHub stars: 20