Deploy
cyanfish-x/tellux
Deploy tellux examples/docs sites via project scripts — one local command (pnpm run deploy) rclone-syncs to the self-hosted site then Wrangler Direct Uploads to Cloudflare Pages.
How to author AsciiDoc content in a docouture Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards…
Install Docouture Writing Docs Pages
$ npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install InditexTech/weavejs docouture-writing-docs-pages --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docouture-writing-docs-pages .claude/skills/docouture-writing-docs-pages && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "docouture-writing-docs-pages" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pages into .claude/skills/docouture-writing-docs-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docouture-writing-docs-pages", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pagesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install InditexTech/weavejs docouture-writing-docs-pages --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/docouture-writing-docs-pages .agents/skills/docouture-writing-docs-pages && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docouture-writing-docs-pages" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pages into .agents/skills/docouture-writing-docs-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docouture-writing-docs-pages", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install InditexTech/weavejs docouture-writing-docs-pages --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/docouture-writing-docs-pages .cursor/skills/docouture-writing-docs-pages && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "docouture-writing-docs-pages" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pages into .cursor/skills/docouture-writing-docs-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docouture-writing-docs-pages", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/InditexTech/weavejs.git --path .agents/skills/docouture-writing-docs-pages--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install InditexTech/weavejs docouture-writing-docs-pages --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/docouture-writing-docs-pages .gemini/skills/docouture-writing-docs-pages && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "docouture-writing-docs-pages" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pages into .gemini/skills/docouture-writing-docs-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docouture-writing-docs-pages", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install InditexTech/weavejs docouture-writing-docs-pagesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/docouture-writing-docs-pages .github/skills/docouture-writing-docs-pages && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "docouture-writing-docs-pages" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pages into .github/skills/docouture-writing-docs-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docouture-writing-docs-pages", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install InditexTech/weavejs docouture-writing-docs-pages --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/docouture-writing-docs-pages .opencode/skills/docouture-writing-docs-pages && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "docouture-writing-docs-pages" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/docouture-writing-docs-pages into .opencode/skills/docouture-writing-docs-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docouture-writing-docs-pages", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
docouture-writing-docs-pages- GitHub stars
- 226
- Token cost
- ~3.1k tokens
- SKILL.md length
- 995 words
- Files
- 3
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
How to author AsciiDoc content in a docouture Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards…
- Editing a .adoc page
- SKILL.md covers Where content lives, Resource IDs, Where a change goes and Nesting rule: keep a section's…, plus 3 more sections
- Reaches docs.asciidoctor.org and antora.org
- Adding a page to the nav
What it does
Docouture Writing Docs Pages is an agent skill from InditexTech/weavejs. How to author AsciiDoc content in a docouture Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards, accordion, feature-tabs, cta, label:/mono: macros). USE WHEN writing or editing a .adoc page, adding a page to the nav, fixing a broken xref, or reaching for a block like tabs/cards/accordion. EXAMPLES: 'add a page', 'my xref doesn't resolve', 'the build fails on a warning', 'add tabs for pnpm/npm/yarn commands', 'group…
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `reference/docouture-blocks.md` and `reference/language-basics.md`).
It sits in Sales & Support, covering Static sites and blogs and Help center and FAQ content. It works with npm and pnpm. The repository describes itself as: Weave.js is an open source library to build real-time collaboration applications like whiteboards, diagram editors, etc. on HTML5 Canvas with your own UI. The licence is Apache-2.0.
When your agent uses it
- Editing a .adoc page
- Adding a page to the nav
- Fixing a broken xref
- Reaching for a block like tabs/cards/accordion
Example prompts
- “add a page”
- “my xref doesn”
- “the build fails on a warning”
- “/docouture-writing-docs-pages”
What it can do on your machine
Read from SKILL.md and the folder at commit 2bd3672. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are adoc).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.asciidoctor.organtora.orgkroki.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Docouture Writing Docs Pages loads about 3.1k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 995 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from InditexTech/weavejs at commit 2bd3672, republished under its Apache-2.0 licence (© InditexTech). 995 words, ~3,143 tokens.
Download SKILL.mdSave it as
.claude/skills/docouture-writing-docs-pages/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- docouture-writing-docs-pages
- description
- How to author AsciiDoc content in a docouture Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards, accordion, feature-tabs, cta, label:/mono: macros). USE WHEN writing or editing a .adoc page, adding a page to the nav, fixing a broken xref, or reaching for a block like tabs/cards/accordion. EXAMPLES: 'add a page', 'my xref doesn't resolve', 'the build fails on a warning', 'add tabs for pnpm/npm/yarn commands', 'group these FAQ items', 'add a card grid'.
Writing docs pages
Every page here is AsciiDoc, parsed by Asciidoctor and orchestrated by Antora. Antora restricts and reinterprets parts of the language (includes, xrefs, image paths); where this skill and the upstream Asciidoctor docs differ, follow this skill.
reference/language-basics.md— the AsciiDoc language itself: document structure, blocks, text formatting, lists, links/xrefs, images, source blocks, admonitions, tables, includes, conditionals, substitutions, attributes — plus a URL index intohttps://docs.asciidoctor.org/asciidoc/latest/for anything not covered.reference/docouture-blocks.md— this site's own custom blocks, registered via@inditextech/docouture-asciidoc-extensions(seeantora-playbook.yml'sasciidoc.extensions):[tabs],[cards],[accordion],[feature-tabs],[cta],label:/mono:inline macros, and a few table/video sizing attributes.
For the home page vs. content page patterns, mono- vs. multi-module sites, and the
playbook/component-descriptor mechanics, see the docouture-docs-internals skill.
Where content lives
docs/src/
antora.yml component descriptor: name, title, version, nav
modules/
ROOT/ the home page only — see docouture-docs-internals
main/ the default content module; every other section starts here
nav.adoc the navigation tree for this module
pages/*.adoc one page per file — these become site URLsOnly pages/ exists in a freshly scaffolded site. The other family directories are
created when first needed, with these exact names — Antora keys off them and ignores
anything else:
| directory | family | referenced as |
|---|---|---|
pages/ | page$ | xref:name.adoc[] |
partials/ | partial$ | include::partial$name.adoc[] |
examples/ | example$ | include::example$name.json[] |
images/ | image$ | image::name.png[] |
attachments/ | attachment$ | xref:attachment$file.pdf[] |
Resource IDs
Antora addresses content by resource ID, not by relative path:
version@component:module:family$relative/path.adoc#fragmentEverything left of the filename is optional and defaults to the current page's context. Inside the same module:
| reference | means |
|---|---|
xref:index.adoc[Home] | a page in the same module |
xref:guide/setup.adoc[] | a page in a subdirectory of pages/ — empty text uses the target's title |
xref:other-module:index.adoc[] | a page in another module — see docouture-docs-internals for when a repo has more than ROOT + main |
xref:index.adoc#install[] | a fragment on another page |
include::partial$intro.adoc[] | a partial from the same module |
../ path traversal between pages is not how this works — a page one directory deep
still addresses its sibling as xref:guide/other.adoc[], module-relative, never
file-relative.
Where a change goes
| you want to | do |
|---|---|
| add a page | create docs/src/modules/<module>/pages/name.adoc and add an xref: to that module's nav.adoc |
| add a section to the nav | edit nav.adoc — nesting is list depth (*, **, ***); a bare, unlinked list item can group xrefs under a heading with no page of its own |
| reuse a chunk of prose | docs/src/modules/<module>/partials/name.adoc, included as partial$name.adoc |
| add an image | docs/src/modules/<module>/images/name.png, referenced as image::name.png[Alt] |
| set a site-wide attribute | asciidoc.attributes in antora-playbook.yml |
| set a component-wide attribute | asciidoc.attributes in docs/src/antora.yml |
| set a page-scoped attribute | an attribute entry in the page header, above the first blank line |
Nesting rule: keep a section's Overview flat
Nesting in nav.adoc is literal list-marker depth (*, **, ***) — Antora has no
concept of "this line is an Overview page," so indenting a topic one level under it reads
exactly like indenting it under anything else. A section's own Overview/index page stays
a flat sibling of that section's other top-level pages — it is never their parent.
Nesting only happens one level below a page that genuinely owns sub-pages of its own.
This doesn't forbid nesting under an Overview/index page in general — it forbids nesting
other topics under the section's own Overview. A sub-topic's own index page can still
legitimately parent its own children: changelog/index.adoc parenting its per-version
pages is correct, because those pages genuinely belong to the changelog, not to the
section's Overview.
Don't — nests every other topic under Overview:
* Guides
* xref:guides-overview.adoc[Overview]
** xref:configure-authentication.adoc[Configure authentication]
*** xref:configure-authentication-details.adoc[Configure authentication details]Do — Overview stays flat; only a topic's genuine sub-page nests under that topic:
* Guides
* xref:guides-overview.adoc[Overview]
* xref:configure-authentication.adoc[Configure authentication]
** xref:configure-authentication-details.adoc[Configure authentication details]Linking third-party mentions
The first time a page names a third-party product, library, or repo in prose — Antora,
AsciiDoc, Kroki, Shiki, pnpm, GitHub, etc. — link it to its canonical home
(https://antora.org, https://kroki.io, ...). Don't repeat the link on every later
mention on the same page; once is enough. Internal/proprietary tools with no public URL
(e.g. an internal wiki page, a private registry) are named but left unlinked — there's nothing to send
a reader to.
Show full SKILL.md (405 more words)Show less
Constraints that fail silently
- Never touch
docs/build/directly — no editing, norm -rf, ever. It's generated output, not source. Ifdocouture devis running, it owns that directory and rebuilds it live on every save; a separate ad-hocantora/docouture buildinvocation into the same path, or deleting it "to verify a clean build," pulls the directory out from under that running server and breaks what the user is looking at in their browser. To verify a change, trust the runningdevserver's own live-reload — don't build a second copy. - A warning is a build failure.
antora-playbook.ymlsetsruntime.log.failure_level: warn. A broken xref, a missing include target, an undefined attribute reference or a bad image path exits non-zero. - A page missing from
nav.adocstill builds. It publishes at its URL, renders with an empty navigation context and is reachable only by direct link. Nothing warns. include::cannot read arbitrary paths. Antora installs its own include processor that resolves targets against the content catalog, so only the family forms (partial$,example$, page IDs) work. A filesystem path fails at build time.- Attribute references are not substituted inside verbatim blocks.
{version}inside----/....renders literally unless the block carriessubs=attributes+. - Unconstrained formatting needs doubled marks.
**bold**mid-word,__italic__mid-word. The single-mark form adjacent to a word character is not formatting at all. - A cross-module xref only resolves inside a multi-module site, and only once both
modules are listed under
docs/src/antora.yml'snav:— seedocouture-docs-internals.
Page attributes the UI reads
| attribute | effect |
|---|---|
description | hero excerpt (below the title) AND <meta name="description"> |
page-tags | comma-separated; one label pill each in the hero |
page-action / page-action-url | primary hero button — renders only when BOTH are set |
page-action-secondary / page-action-secondary-url | secondary hero button, same rule |
page-hero-image / page-hero-image-alt | hero illustration |
page-hero-video / page-hero-video-poster | hero video (wins over page-hero-image if both are set), with a still shown before it plays |
page-hero-image-bordered | bare, presence-only attribute (no value) — opts either hero media form into a framed panel instead of the default bare slot |
page-nav-module | which module's nav tree the side menu shows for this page — set on ROOT's own landing page, since ROOT never has its own nav.adoc |
page-layout: home | the marketing home-page layout, two-column (hero beside content) — see docouture-docs-internals's page-patterns reference |
page-layout: home-single | the same home-page authoring surface, single-column (hero stacked above content) — pick per site, not a different set of attributes |
page-role: -hero | suppresses the hero entirely |
page-role: -toc | suppresses the right-hand table of contents |
page-pagination | enables the previous/next footer links |
© InditexTech, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in .agents/skills/docouture-writing-docs-pages of InditexTech/weavejs.
- SKILL.md
- reference/docouture-blocks.md
- reference/language-basics.md
Open the folder on GitHubat commit 2bd3672
Compare with similar skills
Docouture Writing Docs Pages next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Docouture Writing Docs Pages this skillInditexTech/weavejs | 226 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Deploycyanfish-x/tellux | 207 | — | ~1.1k | Automated safety check: Notes | MIT | |
| Create Docsvictorgarciaesgi/nuxt-typed-router | 413 | 2 repos | ~2.8k | Automated safety check: Pass | MIT | |
| React Emailviclafouch/meme-studio | 110 | 2 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Skin Developerningbainb/deepseek-harness-desktop | 785 | — | ~1.4k | Automated safety check: Pass | BSD-3-Clause | |
| UI Previewtingly-dev/tingly-box | 351 | — | ~2k | Automated safety check: Notes | MPL-2.0 |
Similar skills
Create Docs
victorgarciaesgi/nuxt-typed-router
Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.
React Email
viclafouch/meme-studio
A skill your agent uses when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.
Skin Developer
ningbainb/deepseek-harness-desktop
Build a new skin for the dsh-web-ui skin collection (DSH Web GUI) and publish it into the skin-center plugin — scaffold with scripts/dsh-skin-new, author skin.json plus the apply/dispose +…
UI Preview
tingly-dev/tingly-box
Capture headless-Chrome screenshots of the tingly-box frontend (running locally in mock mode) so frontend changes can be visually verified in environments without a real browser.
Mdzilla
pi0/mdzilla
Browse, search, and export documentation from any source using the mdzilla CLI.
More from InditexTech/weavejs
All 9 skills in this repoWriting Fragments
InditexTech/weavejs
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for…
Writing Beats
InditexTech/weavejs
Shape an article as a journey of beats, choose-your-own-adventure style.
Docouture Authoring Guides
InditexTech/weavejs
What to write on each page of a docouture documentation site: the purpose of every page, the section skeleton it needs, what to say in each section, a copyable AsciiDoc starting point and a quality…
Writing Shape
InditexTech/weavejs
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format…
Docouture Docs Internals
InditexTech/weavejs
How a docouture Antora documentation site is put together: the playbook, the docs/antora.yml component descriptor, the four names that must agree, the ROOT+main default layout, promoting…
Docouture Documenting Changes
InditexTech/weavejs
How to update an existing docouture documentation site when a feature, change, deprecation or fix lands in the repo — figuring out what's affected from a diff/commit/PR, confirming with the user…
Related
Categories
Questions about Docouture Writing Docs Pages
What does Docouture Writing Docs Pages do?
How to author AsciiDoc content in a docouture Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards…. Docouture Writing Docs Pages is an agent skill from InditexTech/weavejs.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards, accordion, feature-tabs, cta, label:/mono: macros).
When should I use Docouture Writing Docs Pages?
Docouture Writing Docs Pages fits situations like: editing a .adoc page; adding a page to the nav; fixing a broken xref; reaching for a block like tabs/cards/accordion.
How do I install Docouture Writing Docs Pages in Claude Code?
Run `npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a claude-code`. Or copy the skill folder (.agents/skills/docouture-writing-docs-pages in InditexTech/weavejs) into .claude/skills/docouture-writing-docs-pages in your project. Claude Code loads it when a task matches its description.
How do I install Docouture Writing Docs Pages in Codex?
Run `npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a codex`. Or copy the skill folder (.agents/skills/docouture-writing-docs-pages in InditexTech/weavejs) into .agents/skills/docouture-writing-docs-pages in your project. Codex loads it when a task matches its description.
Can I use Docouture Writing Docs Pages in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add InditexTech/weavejs --skill docouture-writing-docs-pages -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docouture-writing-docs-pages, .gemini/skills/docouture-writing-docs-pages, .github/skills/docouture-writing-docs-pages and .opencode/skills/docouture-writing-docs-pages in your project.
What does Docouture Writing Docs Pages need to run?
SKILL.md names no scripts, command-line tools or credentials: Docouture Writing Docs Pages is instructions for the agent only.
Does Docouture Writing Docs Pages access the network?
SKILL.md names 3 domains. In commands or code: docs.asciidoctor.org, antora.org and kroki.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Docouture Writing Docs Pages safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Docouture Writing Docs Pages use?
Docouture Writing Docs Pages is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docouture Writing Docs Pages use?
About 3.1k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Docouture Writing Docs Pages?
Skills that share tags, products or a category with Docouture Writing Docs Pages: Deploy (cyanfish-x/tellux, 207 stars), Create Docs (victorgarciaesgi/nuxt-typed-router, 413 stars), React Email (viclafouch/meme-studio, 110 stars) and Skin Developer (ningbainb/deepseek-harness-desktop, 785 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docouture Writing Docs Pages?
InditexTech (a GitHub organization) maintains it in InditexTech/weavejs, which has 226 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.
Source: InditexTech/weavejs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.