Agent skills for Claude Desktop

Use when preparing the reporting completeness and research-data materials for a Field Crops Research (FCR) manuscript.

Use when preparing the data availability statement and the data/code archive for a Global Change Biology (GCB) manuscript.

Use when targeting Reports on Progress in Physics (RoPP) or deciding whether a physics review manuscript fits this IOP authoritative…

Analyze a repository before runtime experimentation: identify the Node.js application entrypoint, package manager, scripts, HTTP targets…

Investigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments…

Audit a GitHub repository's security posture and hardening gaps across branch protection, CODEOWNERS, GitHub Actions, publish/release…

Manages complex multi-language repository architectures through standardized task commands and automated version synchronization.

Use when targeting Representations or deciding whether a new-historicist or interdisciplinary cultural-analysis manuscript fits this venue.

Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only…

Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence (a screen recording by default), and…

Machine-readable journal format for reproducible data analysis operations

Run or resume a deterministic, source-backed pathology-first programme that identifies existing-drug repurposing hypotheses for a supplied…

Use when the user explicitly approves a GPT-5.6 Sol review of a bounded software diff, branch, commit, design, plan, or research conclusion.

Android native application development and UI design guide.

[UDS] Write user stories and requirements that satisfy the INVEST criteria.

Turn a business requirement document (Word/PDF/Excel/Markdown, plus its attachments) into a written spec and a task breakdown, filed…

Analyze product/feature requirements for the PigeonPod project with software engineering rigor.

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

User stories, acceptance criteria, PRDs, and requirements documentation patterns.

Unless otherwise stated by the user or existing template

Track requirements through their lifecycle from Proposed to Verified, with status distributions and progress reporting.