跳到正文
cccskills
免费在 GitHub 公开

rseng-quality-framework

The entry point and router for this pack: explains the research software quality framework - community-standard quality dimensions, measurable indicators and the three-tier model (analysis code, prototype tools, infrastructure) - and routes to the right companion rseng-* skill. Use PROACTIVELY at the start of any research software task to classify the software's tier and select which practices apply, and whenever the user asks what research software quality means, mentions quality dimensions, indicators or the three-tier model, wants a quality assessment or improvement plan for research software, or is unsure which quality practice to start with.

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills星标 24(GitHub 24 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件（2）

  • SKILL.md12.8 KB
  • references.md499 B

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

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 registry, not from page prose:

community, compatibility, FAIRness, flexibility, functional suitability, interaction capability, maintainability, open source software, performance efficiency, reliability, safety, security, sustainability.

Dimensions are qualitative categories, built on the ISO/IEC 25010 top-level characteristics and extended for research software. Use them to structure an assessment conversation, not as a scoring rubric.

Quality indicators

Each dimension is backed by measurable indicators from the companion registry (https://w3id.org/everse/rsqi); 47 indicators are defined at the pinned upstream version, such as software_has_tests, has_ci-tests, software_has_license, software_has_citation and archived_in_software_heritage. The browsable dimension and indicator tables are published at (https://everse.software/indicators/website/indicators.html and .../dimensions.html). Indicators are proxies: passing them is evidence of quality, not proof.

Running an indicator-based assessment

When asked to "check quality" or assess a repository, run a structured pass rather than an impression:

  1. Establish the tier first (above) - roughly a third of the indicators are not applicable to analysis code, and reporting them as failures demoralizes rather than helps.
  2. Walk the indicators per dimension and mark each met / unmet / not-applicable-for-tier, with one line of evidence per verdict (the file, badge, workflow or record that proves it).
  3. Route every unmet indicator to the sibling skill that fixes it (the dimension map below); the quantitative cluster - complexity, duplication, cohesion/coupling, churn, maintainability index, size and documentation-coverage conventions - is measured by rseng-software-metrics.
  4. Deliver as a prioritized improvement plan, cheapest-first within the tier's expectations, not as a scorecard - and rerun after fixes to report the delta (the same assess-fix-reassess loop as rseng-fairguard).

Dimension-to-skill map

  • Community: rseng-community-governance, rseng-science-communication
  • Compatibility: rseng-scientific-file-formats, rseng-reproducible-environments
  • FAIRness: rseng-fair-software, rseng-fairguard, rseng-citation-metadata, rseng-fair-ml
  • Flexibility: rseng-software-design, rseng-reproducible-environments
  • Functional suitability: rseng-testing, rseng-defensive-coding
  • Interaction capability: rseng-ux-accessibility
  • Maintainability: rseng-code-quality, rseng-software-metrics, rseng-software-design, rseng-maintenance-sustainability
  • Open source software: rseng-licensing, rseng-license-compliance, rseng-community-governance
  • Performance efficiency: rseng-performance-profiling, rseng-gpu-computing, rseng-big-data-processing
  • Reliability: rseng-testing, rseng-debugging, rseng-defensive-coding
  • Safety: no dedicated skill - for software whose failure can harm people or property, flag it and route to domain safety processes
  • Security: rseng-security, rseng-agent-security, rseng-regulatory-compliance
  • Sustainability: rseng-maintenance-sustainability, rseng-archiving, rseng-green-computing, rseng-management-planning

The software life cycle

Quality practices attach to life-cycle stages: planning, development, testing, release, maintenance, retirement. When the user is at a specific stage, prefer stage-appropriate advice - a retirement conversation is about archiving and handover, not about adding CI.

Role-based entry points

Match advice to who is asking: researcher who codes (version control, README, pinned environment, basic tests first; grow from there), research software engineer (full engineering practice), principal investigator (management plans, credit policy, sustainability and staffing), project manager (milestones tied to releases, quality gates, maintenance backlog), policy maker (software as a recognized research output), trainer (curricula from the task pages, Carpentries and CodeRefinery style).

Which sibling skill to use

Route concrete tasks to the specialised skill:

<!-- skill-directory:start (generated - do not edit by hand) -->

Core engineering:

  • rseng-testing: how to test research software
  • rseng-ci-cd: continuous integration and delivery for research software
  • rseng-code-quality: writing readable research code and structuring software projects
  • rseng-software-design: designing research software
  • rseng-defensive-coding: defenses against silently wrong research results
  • rseng-debugging: systematic debugging of research software
  • rseng-version-control-review: using version control effectively for research software and the PR-time review process
  • rseng-software-metrics: measuring code health quantitatively
  • rseng-pair-programming: the agent as an effective pair programmer and pull-request review buddy for research software
  • rseng-code-review: reviewing existing code and whole projects, not just new diffs
  • rseng-project-scaffolding: starting research software projects from maintained templates and keeping them in sync

Reproducibility and workflows:

  • rseng-reproducible-environments: making research software environments reproducible
  • rseng-reproducibility: end-to-end computational reproducibility
  • rseng-workflows: building, choosing, discovering, describing, and sharing computational workflows with workflow management...
  • rseng-provenance: capturing and packaging the provenance of software and data
  • rseng-notebooks: engineering discipline for computational notebooks

Research data:

  • rseng-data-management: research data management around software
  • rseng-scientific-file-formats: choosing and handling scientific data formats in code
  • rseng-big-data-processing: processing research data that outgrows one machine's memory
  • rseng-data-management-plans: data management plans (DMPs) for research projects

Numerics and performance:

  • rseng-numerical-accuracy: floating-point correctness in research code
  • rseng-performance-profiling: making research code faster with evidence
  • rseng-gpu-computing: GPU and accelerator programming for research software
  • rseng-hpc-computing: working effectively on high-performance computing clusters

Publishing, credit and reuse:

  • rseng-publishing-releasing: the release lifecycle of research software
  • rseng-software-publishing: publishing research software through its distribution channels
  • rseng-archiving: long-term archiving of research software and data
  • rseng-citation-metadata: making research software citable and contributors credited
  • rseng-citation-hygiene: verifying that every citation is real, correct and current
  • rseng-licensing: how to license research software
  • rseng-license-compliance: license compliance engineering
  • rseng-fair-software: how to apply the FAIR principles - findable, accessible, interoperable, reusable - to research software...
  • rseng-fair-ml: applying FAIR principles to machine learning artifacts
  • rseng-fairguard: assessing research software against the 17 FAIR4RS principles with FAIRGuard (https://www.fairguard.org)
  • rseng-software-reuse: discovering and reusing existing research software instead of rebuilding it...
  • rseng-discovery: discovering the research landscape around a topic or project
  • rseng-dependency-management: the full lifecycle of third-party dependencies
  • rseng-software-peer-review: community peer review of research software
  • rseng-open-science-practices: the researcher-facing open science workflow

Integrity, security and compliance:

  • rseng-security: securing research software and its supply chain
  • rseng-agent-security: operating AI coding agents securely
  • rseng-regulatory-compliance: checking research code and data against data-protection and AI regulation
  • rseng-research-integrity: integrity checks on research outputs before submission or release
  • rseng-fact-checking: verifying facts and sources at the content level
  • rseng-honesty: responding when concealment or misrepresentation is requested
  • rseng-human-verification: the human's side of AI-assisted research software
  • rseng-ai-declaration: declaring AI involvement with the AI Declaration Format (https://ai-declaration.org)

Community and people:

  • rseng-community-governance: building and governing a community around research software
  • rseng-community-metrics: measuring community health with CHAOSS-style metrics
  • rseng-contributor-onboarding: turning users into contributors and contributors into regulars
  • rseng-user-support: running user support as an operation for research software
  • rseng-trainer: teaching research software skills while working

Communication and interfaces:

  • rseng-documentation: how to document research software at every level
  • rseng-science-communication: communicating research software outward to research audiences
  • rseng-storytelling: telling the story of research data, software and projects to broad audiences
  • rseng-ux-accessibility: user experience and accessibility for research software

Planning and operations:

  • rseng-management-planning: planning research software work
  • rseng-project-kickoff: starting a new research software project with a short kickoff interview
  • rseng-project-tracking: the operational side of running a research software project
  • rseng-lessons-learned: capturing and reusing what a project learns
  • rseng-maintenance-sustainability: keeping research software alive and responsible over time
  • rseng-green-computing: the environmental footprint of research computing

Specialized:

  • rseng-language-guides: language-specific research software practice
  • rseng-legacy-code: working safely with inherited research code
  • rseng-open-source-migration: migrating research code from commercial, license-bound platforms to open source alternatives
  • rseng-scientific-visualization: visualization of scientific data beyond publication figures
<!-- skill-directory:end -->

Working with this skill

  • references.md - source citations and links to the upstream framework pages

Learn more (verified):

<!-- related-skills:begin -->

Related skills

Check whether any of these applies before moving on:

  • rseng-fair-software - FAIRness dimension practice
  • rseng-fairguard - FAIR assess-fix-reassess sibling loop
  • rseng-management-planning - tier drives plan rigor
  • rseng-project-kickoff - new projects pair tiering with interview
  • rseng-software-metrics - quantitative indicator measurement
  • rseng-testing - most common first unmet indicator
<!-- related-skills:end -->

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

rseng-agent-security

免费

Covers operating AI coding agents securely: auditing whether the agent runs sandboxed, permission and dangerous-command configuration, containerized environments, secrets kept out of context, network egress and token privileges, prompt-injection risk, and the privacy of agent use itself. Use PROACTIVELY when permission gating is broadly disabled (skip-permissions modes), when secrets are visible to the agent's shell, or when the agent processes untrusted code, issues or web content; when a project holds personal or confidential data while a cloud agent is active (what leaves the machine, retention, training use), or when the user asks how to run coding agents safely or privately. (Supply-chain security: rseng-security; disclosing agent contributions: rseng-ai-declaration.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

rseng-ai-declaration

免费

Covers declaring AI involvement with the AI Declaration Format (https://ai-declaration.org): creating and maintaining an aidecl.yaml that records which AI tools and agents were used, what each contributed, when and how much, plus the README disclosure footnote, JSON/JSON-LD export and CI validation. Machine-readable disclosure is the practice; this format is one implementation. Use PROACTIVELY when an AI assistant or agent creates or modifies a project's content - generate aidecl.yaml if missing, update it after AI-assisted changes. Also use when the user asks about AI transparency, provenance, disclosure or EU AI Act disclosure, wants to state that NO AI was used, or mentions aidecl. For concealment requests see rseng-honesty; for the human review duty see rseng-human-verification.

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

rseng-archiving

免费

Covers long-term archiving of research software and data: Software Heritage save requests and SWHID persistent identifiers, Zenodo deposits with versioned DOIs and forge integration, choosing domain and institutional repositories, deciding what to archive (code, data, environments, documentation) and when, and archiving at project retirement. Use when the user wants software or data preserved beyond the life of a forge account, grant or lab, mentions Software Heritage, SWHIDs, Zenodo deposits or archiving, retires or hands over a project, prepares artifacts that must stay resolvable for a paper, or when funder policy requires long-term preservation. (Cutting the release itself is rseng-publishing-releasing; day-to-day data storage and repository choice is rseng-data-management.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

rseng-big-data-processing

免费

Covers processing research data that outgrows one machine's memory: out-of-core and chunked computation, Dask for scaling the scientific Python stack, Spark for distributed tabular pipelines, lazy evaluation, partitioning strategies, idempotent and restartable batch jobs, and knowing when NOT to distribute. Use when datasets no longer fit in memory, when the user mentions Dask, Spark, out-of-core or larger-than-memory data, when a pandas/NumPy workflow hits memory limits, or when designing batch pipelines over many files. (Cluster job submission and job arrays are rseng-hpc-computing; pipeline orchestration engines are rseng-workflows; profile first with rseng-performance-profiling.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

rseng-ci-cd

免费

Covers continuous integration and delivery for research software: CI/CD concepts, automating builds and tests with GitHub Actions and GitLab CI/CD, and wiring an organization's GitLab CI infrastructure to a GitHub-hosted project. Use when the user asks to set up CI, write a pipeline or workflow file (.github/workflows, .gitlab-ci.yml), add automated builds/tests on push or pull request, publish a package or deploy docs when a tag or release is cut, cache dependencies to speed up CI runs, choose between GitHub Actions and GitLab CI, use self-hosted or GPU runners, mirror a repo, or report external CI status back to GitHub. For what to test and shrinking a test matrix see rseng-testing; for linter and pre-commit policy see rseng-code-quality.

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

rseng-citation-hygiene

免费

Covers verifying that every citation is real, correct and current: checking references in manuscripts, READMEs, references files and code metadata against Crossref and OpenAlex, screening cited DOIs against the Retraction Watch database, catching fabricated or mis-attributed citations (a documented AI failure mode), and keeping bibliographies and CITATION.cff files resolvable. Use PROACTIVELY before any bibliography, reference list or citation metadata is finalized or published, whenever the agent itself has produced citations, and when the user asks to check references, mentions broken DOIs, retracted papers or citation verification, or prepares a manuscript, README or software paper with references. (Making your own software citable is rseng-citation-metadata.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

查看 fdiblen 的全部技能

报告此技能的问题