skills.rest
BKZhao
BKZhaoCOMMUNITY
Explore all skills by this author →
GitHub

clinical-capability-expansion

Formalize paper-facing gaps into reusable method families with executable scaffolds.

Updated Aug 27, 2026
Search Tags:#clinical#capability#artifact-delivery#reuse#paper-processing#method-family#runtime-scaffolds
One-click install
npx skills add https://github.com/BKZhao/-mimic-repo-agent --skill clinical-capability-expansion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clinical-capability-expansion
Source: https://github.com/BKZhao/-mimic-repo-agent/tree/main/.codex/skills/clinical-capability-expansion
Command: npx skills add https://github.com/BKZhao/-mimic-repo-agent --skill clinical-capability-expansion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn clinical gaps in a manuscript or workflow into reusable capability by formalizing an unclear method or artifact into a stable, promotable family that can be executed locally.

Core Features & Use Cases

  • Normalize a paper-specific gap into a reusable capability by mapping it to a method family and executable scaffolds.
  • Decide routing, execution, and delivery surfaces to ensure future reuse, testing, and artifact packaging.
  • Promote a gap into a native capability with explicit artifact contracts and a delivery surface for users.

Quick Start

Freeze the paper-facing request, normalize the method family, and generate a local scaffold for reusable capability.

Frequently Asked Questions about clinical-capability-expansion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a clinical method gap in a paper into a reusable capability?▼

A clinical gap is formalized by mapping an unclear method or artifact to a stable method family and executable scaffolds, ensuring future reuse, testing, and artifact packaging through defined contracts.

How does artifact delivery work for paper-facing requests with missing capabilities?▼

Routing, execution, and delivery surfaces are decided during the normalization process to ensure the newly promoted capability has explicit artifact contracts, guardrails, and tests for reliable artifact delivery.

Can I use runtime scaffolds to execute a method family locally for clinical workflows?▼

Runtime scaffolds enable local execution by absorbing the paper-facing request, formalizing it into a stable method family, and generating a local scaffold with defined delivery surfaces and user guardrails.

Do I need existing native capabilities to process a clinical paper with method gaps?▼

This approach is required when existing native capabilities do not fully deliver the requested method or artifact, meaning you must absorb the gap and scaffold it into a reusable native capability.

What is the best way to promote a paper-specific gap into a native capability?▼

Promoting a gap into a native capability involves formalizing the gap into a stable method family, applying runtime scaffolds for local execution, and ensuring updates to routing, delivery, and user surface with tests.

When should I not use runtime scaffolds for clinical paper processing?▼

Avoid this approach when the paper-facing request does not present a gap in existing native capabilities, as the process specifically targets methods or artifacts not fully delivered by current capabilities.

Related Skills

Explore More Software Engineering Skills→
lix965996-artlix965996-art

paper-plan

Generate a structured paper outline with claims-evidence matrix and citation scaffolding.

Community
Advanced
systeminitsysteminit
530

swamp-workflow

Manage Swamp workflows for defining, validating, and executing job sequences.

Official
Advanced
lwndevlwndev
2

executing-qa

Execute adversarial QA on feature branches and generate version-2 results artifacts.

Community
Advanced
owenliangowenliang
19

arxiv-search

Search arXiv by keyword and retrieve paper titles and summaries.

Community
Intermediate