SKILL_IDENTIFIER

Provides a canonical template for authoring computational-biology skill units with validated frontmatter.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/tony-zhelonkin/scio --skill skill-identifier-tony-zhelonkin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SKILL_IDENTIFIER
Source: https://github.com/tony-zhelonkin/scio/tree/main/templates/skill
Command: npx skills add https://github.com/tony-zhelonkin/scio --skill skill-identifier-tony-zhelonkin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Authors of computational-biology skills repeatedly re-derive the same SKILL.md structure, frontmatter rules, and section conventions, leading to inconsistent skills that fail validation or route poorly during skill selection. ## Core Features & Use Cases - Canonical frontmatter template: Documents the allowed keys (name, description, license, allowed-tools), the kebab-case naming rule, and the 350-character description cap enforced by the toolkit linter. - Structured body scaffold: Provides ready-made sections for Overview, Decision Tree, Quick Start, Progressive Depth (basic/intermediate/advanced), Verification Checklist, Common Pitfalls, and See also cross-references. - Companion directory conventions: Includes README guidance for references/, scripts/, checks/, and assets/ so authors know what belongs in each on-demand resource directory. - Use Case: A bioinformatician adding a new scanpy or scVI skill to the scio catalog copies this template, renames the placeholder to a kebab-case identifier, fills in the sections, and validates with quick_validate.py before committing. ## Quick Start Copy the templates/skill directory to a new kebab-case skill folder, replace SKILL_IDENTIFIER with the real name, fill in the description and body sections, then run the quick_validate.py script to confirm it passes.

Frequently Asked Questions about SKILL_IDENTIFIER

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

FAQPage Schema
How do I create a new skill for the scio toolkit?▼

Copy the templates/skill directory, rename it to a kebab-case identifier, and replace the SKILL_IDENTIFIER placeholder in the frontmatter. Fill in the description and body sections, then validate with quick_validate.py before committing.

What frontmatter fields are allowed in a SKILL.md file?▼

Only name, description, license, and allowed-tools are permitted as top-level keys. Any other key fails validation; cross-references and caveats belong in body sections like See also or When not to use.

How long can a skill description be?▼

The description is capped at 350 characters, enforced by the toolkit lint check. It should start with the tool name, include a concrete use-when trigger, and point to sibling skills for adjacent cases.

Why does skill validation fail on a fresh template copy?▼

The validator intentionally fails on the placeholder name SKILL_IDENTIFIER to force authors to pick a real kebab-case name matching the directory. Renaming the skill resolves the failure; all other fields already validate.

When should a skill include a decision tree section?▼

A decision tree is optional for simple-tier skills but required for standard and rich tiers. It routes users between this skill, alternative skills, and ad-hoc code based on concrete conditions.