cwl-create-commandlinetool

Generate CWL CommandLineTool YAML definitions with inputs, outputs, and requirements.

30|6|Updated Mar 5, 2019
One-click install
npx skills add https://github.com/crim-ca/weaver --skill cwl-create-commandlinetool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cwl-create-commandlinetool
Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/cwl-create-commandlinetool
Command: npx skills add https://github.com/crim-ca/weaver --skill cwl-create-commandlinetool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the creation of CWL CommandLineTool packages, providing a structured framework for input, output, and execution requirements.

Core Features & Use Cases

  • Structured CWL Creation: Automates the generation of CWL CommandLineTool YAML from scratch.
  • Inputs & Outputs Configuration: Offers templates for defining inputs and outputs, including file and command-line parameters.
  • Requirements Definition: Allows the specification of Docker, environment variables, and resource requirements.
  • Use Case: When developing a new command-line tool that needs to be wrapped as a CWL tool for integration with workflow engines like CWL.

Quick Start

Create a new CWL CommandLineTool package for your command-line tool 'example-tool'.

Frequently Asked Questions about cwl-create-commandlinetool

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

FAQPage Schema
How do I create a CWL CommandLineTool wrapper for a command-line tool?▼

To create a CWL CommandLineTool wrapper, define the tool's inputs, outputs, and execution requirements in a YAML file. This Skill automates that YAML generation from scratch, providing structured templates for command-line parameters and file configurations.

What is a CWL CommandLineTool package used for?▼

A CWL CommandLineTool package is used to wrap command-line software for integration with Common Workflow Language engines. It defines how to execute the tool, specifying inputs, outputs, and runtime environments like Docker containers for workflow systems.

How do I specify Docker and environment variables in a CWL CommandLineTool?▼

Specify Docker and environment variables in a CWL CommandLineTool by defining them within the execution requirements section of the YAML. This Skill provides templates to configure resource requirements, Docker images, and environment variables for tool execution.

Can I use this to generate CWL YAML definitions for tools with complex file inputs?▼

Yes, you can generate CWL YAML definitions for tools with complex file inputs. The Skill offers input and output configuration templates that handle file parameters and command-line arguments, structuring them correctly for the CommandLineTool specification.

Does this approach generate CWL files from scratch or modify existing definitions?▼

This approach generates CWL CommandLineTool YAML definitions from scratch. It streamlines the creation process by automating the initial framework, allowing developers to define new tool wrappers rather than editing pre-existing CWL files.

When do I need to wrap a command-line tool as a CWL CommandLineTool?▼

You need to wrap a command-line tool as a CWL CommandLineTool when integrating standalone software into a Common Workflow Language pipeline. This is required for workflow engines to properly parse inputs, manage execution requirements, and route outputs.