doc-skill-creator

Included with Lifetime

$97 forever

Use this skill when the user wants to convert one or more existing documents into a dedicated skill, including analyzing suitability, extracting capabilities, designing the skill structure, and drafting SKILL.md and references.

Writing & Docs

What this skill does

# doc-skill-creator

## Purpose

Convert existing documents into a dedicated skill design.

This skill is for turning static documentation such as component library docs, SDK docs, utility docs, FAQ, migration guides, standards docs, README files, and examples into practical skill artifacts.

## Use this skill when

Use this skill when the user wants to:

- convert documents into a dedicated skill
- generate a skill from library, SDK, FAQ, migration, or standards documentation
- design a target skill from existing docs
- create SKILL.md and references from source documents
- transform static docs into practical usage capabilities

## Do not use this skill when

Do not use this skill when:

- the user only wants a summary, translation, or rewrite
- the user wants direct usage help instead of creating a skill
- the request is unrelated to documentation-to-skill conversion

## Default workflow

1. Analyze the source material and scope
2. Judge suitability for skill conversion
3. Determine the target skill type
4. Extract capability units
5. Split knowledge into facts, rules, scenarios, examples, pitfalls, migration, and gaps when applicable
6. Design the target skill structure
7. Draft the target SKILL.md and references plan

## Output requirements

Unless the user requests otherwise, include:

1. source material analysis
2. suitability judgment
3. recommended target skill type
4. target skill definition
5. capability map
6. knowledge-layer breakdown
7. suggested references structure
8. draft SKILL.md
9. gaps and follow-up suggestions

## Working rules

- Convert documentation into capabilities, not just summaries
- Organize outputs around user tasks, not source headings
- Prefer practical guidance over passive description
- Clearly separate documented facts from derived guidance
- Do not invent unsupported APIs, features, or guarantees
- State missing information explicitly when the source material is incomplete
- Keep the target skill scoped and maintainable
- If the material spans multiple distinct domains, consider proposing multiple skills instead of one overloaded skill

## References

See `references/` for detailed guidance on analysis, skill typing, capability extraction, knowledge layering, references planning, output templates, examples, pitfalls, gaps, and migration.

Files: 10

Size: 11.7 KB

Complexity: 34/100

Category: Writing & Docs

Source: https://github.com/hubvue/skills/tree/main/productivity/doc-skill-creator

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts