Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
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…
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add InditexTech/weavejs --skill writing-fragments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install InditexTech/weavejs writing-fragments --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/writing-fragments .claude/skills/writing-fragments && 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 "writing-fragments" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/writing-fragments into .claude/skills/writing-fragments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-fragments", 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/writing-fragmentsType 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 writing-fragments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install InditexTech/weavejs writing-fragments --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/writing-fragments .agents/skills/writing-fragments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-fragments" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/writing-fragments into .agents/skills/writing-fragments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-fragments", 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 writing-fragments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install InditexTech/weavejs writing-fragments --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/writing-fragments .cursor/skills/writing-fragments && 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 "writing-fragments" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/writing-fragments into .cursor/skills/writing-fragments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-fragments", 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/writing-fragments--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 writing-fragments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install InditexTech/weavejs writing-fragments --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/writing-fragments .gemini/skills/writing-fragments && 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 "writing-fragments" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/writing-fragments into .gemini/skills/writing-fragments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-fragments", 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 writing-fragmentsInstalls 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 writing-fragments -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/writing-fragments .github/skills/writing-fragments && 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 "writing-fragments" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/writing-fragments into .github/skills/writing-fragments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-fragments", 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 writing-fragments -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 writing-fragments --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/writing-fragments .opencode/skills/writing-fragments && 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 "writing-fragments" agent skill from https://github.com/InditexTech/weavejs/tree/main/.agents/skills/writing-fragments into .opencode/skills/writing-fragments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-fragments", 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.
writing-fragmentsGrilling 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 Fragments is an agent skill from 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 a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Requirements gathering. 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.
Read from SKILL.md and the folder at commit 2bd3672. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Writing Fragments loads about 828 tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 414 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.
The automated check found patterns that need a careful read before installing.
Append silently. Don't ask permission for each fragment. Mention what you added in passing ("adding that"), but don't inAutomated 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.
The full file from InditexTech/weavejs at commit 2bd3672, republished under its Apache-2.0 licence (© InditexTech). 414 words, ~828 tokens.
.claude/skills/writing-fragments/SKILL.md (or your agent's skills folder).<what-to-do>
Run a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope.
As fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved.
If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.
Capture fragments from the very first thing the user says, including the initial prompt.
On first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date.
</what-to-do>
<supporting-info>
A fragment is any piece of text that might survive into the final article. It must be readable by the author — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is "is this a piece of good writing?", not "is this a self-contained argument?"
Fragments are deliberately heterogeneous. Examples of what could be a fragment:
The novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.
# Working title
A first fragment lives here.
It can be multiple paragraphs. It can include lists, code, quotes — whatever
shape the fragment naturally takes.
---
A second fragment.
---
> A quoted line that the user wants to keep around.
A reaction to it.
---
- A cluster of related observations
- That hang together by feel
- And want to be near each otherFragments are separated by a horizontal rule (\n---\n). No headings inside the body. No tags. No order beyond the order they were added.
Append silently. Don't ask permission for each fragment. Mention what you added in passing ("adding that"), but don't interrupt the conversation with save dialogs.
Before every write: re-read the file from disk. The user may have edited, reordered, or deleted fragments between turns — preserve their changes. Never overwrite the file; only append (or, if the user asks, edit a specific fragment in place).
The user can say "cut the last one", "rewrite that one sharper", "merge those two" at any time. Treat those as first-class instructions.
</supporting-info>
© 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
Just SKILL.md in .agents/skills/writing-fragments of InditexTech/weavejs.
Open the folder on GitHubat commit 2bd3672
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in InditexTech/weavejs, which our catalogue first saw on October 7, 2026.
Writing Fragments 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 |
|---|---|---|---|---|---|---|
| Writing Fragments this skillInditexTech/weavejs | 226 | 4 repos | ~828 | Automated safety check: Warn | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 103k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Grillingpietheinstrengholt/rssmonster | 564 | 31 repos | ~510 | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 |
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
pietheinstrengholt/rssmonster
Grill the user relentlessly about a plan, decision, or idea.
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
InditexTech/weavejs
Shape an article as a journey of beats, choose-your-own-adventure style.
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…
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…
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…
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…
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…
Categories
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 Fragments is an agent skill from 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 a future article.
Writing Fragments fits situations like: the user wants to develop ideas before imposing structure; mentions fragments; raw material for writing.
Run `npx skills add InditexTech/weavejs --skill writing-fragments -a claude-code`. Or copy the skill folder (.agents/skills/writing-fragments in InditexTech/weavejs) into .claude/skills/writing-fragments in your project. Claude Code loads it when a task matches its description.
Run `npx skills add InditexTech/weavejs --skill writing-fragments -a codex`. Or copy the skill folder (.agents/skills/writing-fragments in InditexTech/weavejs) into .agents/skills/writing-fragments in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add InditexTech/weavejs --skill writing-fragments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-fragments, .gemini/skills/writing-fragments, .github/skills/writing-fragments and .opencode/skills/writing-fragments in your project.
SKILL.md names no scripts, command-line tools or credentials: Writing Fragments is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.
Writing Fragments 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.
About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Writing Fragments: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.