rseng-quality-frameworklisted

# Research software quality framework This skill is the entry point to the pack. It explains a community-standard framing of research software quality and points to the specialised sibling skills for concrete tasks. Ground every quality discussion in two questions: what tier of software is this, and which quality dimensions matter for it right now. ## The three-tier view Classify the software before recommending practices; expectations scale with intent, not with code size. - Tier 1, analysis code: scripts and notebooks capturing a computational method for a paper or dataset, often single-author. Quality floor: version control, a README stating purpose and how to run, a pinned environment, a license, and a citation entry. - Tier 2, prototype tools: software demonstrating a method for use beyond its origin project, multiple users or contributors. Add: tests with CI, structured documentation, releases with versioning, contribution notes. - Tier 3, research software infrastructure: services, libraries and frameworks that communities depend on. Add: governance, review process, security and maintenance policy, sustainability planning, archiving. Software moves between tiers; when analysis code starts being reused, recommend upgrading its practices tier by tier rather than all at once. ## Quality dimensions The framework defines 13 quality dimensions, formally published as a JSON-LD registry (https://w3id.org/everse/rsqd). Always take names and counts from the