Chrisai docing

Skill cblanquera/chrisai/skills/chrisai-docing

Me + LLM = Godly

Install

npx -y skills add cblanquera/chrisai --skill chrisai-docing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use for technical writing tasks that include guided learning, API reference, formatting, or copy editing for technical readers.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, as published. Nobody here has run it

ChrisAI Docing

Use this skill for technical writing and developer-facing technical documentation. Route the task to the narrowest internal workflow or reference unless the request clearly needs a deliberate sequence.

Do not use this skill for general documentation tasks such as business docs, marketing copy, operational policy, project planning notes, or non-technical knowledge-base writing unless the user explicitly asks to treat that material as developer-facing technical documentation.

Do not treat the workflow and reference files as separate skills. They are internal guidance for this consolidated skill.

Internal Guidance

Use workflows/copy-editing.md when the user asks to proofread, tighten, clarify, simplify, or improve existing documentation without changing its technical meaning or owning its information architecture.
Use references/guided-learning.md when the user asks to create or restructure quick starts, tutorials, getting-started guides, conceptual explanations, first-success flows, reader journeys, teaching style, guided walkthroughs, or progressive-disclosure docs.
Use references/api-reference.md when the user asks to write, restructure, or review lookup-oriented docs for APIs, modules, classes, functions, methods, CLI commands, config, schemas, parameters, return values, errors, or typed usage examples.
Use references/formatting.md when the user asks to normalize markdown presentation after the content strategy is clear, including headings, TOCs, outline numbering, spacing, list style, code fence language tags, links, anchors, and repo style-guide conformance.

Sequencing

Only chain internal guidance when there is a clear owner plus a clear follow-up. Use this order:

references/guided-learning.md or references/api-reference.md first when the task needs content ownership.
workflows/copy-editing.md second when the prose needs an editorial pass.
references/formatting.md last when the output still needs markdown or structure cleanup.

Do not default to multi-step documentation sequences.

Decision Rules

If the request mixes guided learning and reference, choose the primary user goal first; only add formatting later if needed.
If the request is mainly about proofreading, clarity, transitions, or tone rather than document ownership, use workflows/copy-editing.md.
If the request is mainly about lookup-oriented API, class, module, function, configuration, or typed example material, use references/api-reference.md.
If the request is mainly about a quick start, tutorial, conceptual guide, or junior-developer learning path, use references/guided-learning.md.
If the document type is already correct and the task is markdown structure, outline numbering, links, TOC, spacing, or style cleanup, use references/formatting.md.