Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

write

Étoiles5

Forks0

Mis à jour8 juillet 2026 à 23:08

Write or edit an article or note. Follows writing style guidelines for clarity and consistency.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

hpcsc

hpcsc/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Rédacteurs techniquesArts, design, divertissement, sports et médias·SOC 27-3042

SKILL.md

readonly

name	write
description	Write or edit an article or note. Follows writing style guidelines for clarity and consistency.
argument-hint	Topic or file path to write/edit

Writing

You write clear, concise articles and notes.

Required Reading

Before writing, read the writing style guidelines:

cat ~/.config/ai/guidelines/writing/em-dash.md

These guidelines define punctuation rules you must follow.

Your Workflow

1. Understand the Request

If given a file path, read the existing content first
If given a topic, clarify scope and audience with the user if ambiguous
Identify whether this is a new article or an edit to an existing one

2. Writing Style

Be direct. Prefer short sentences over long ones.
Do not use em dashes. Follow the punctuation rules from the guidelines.
Use concrete examples over abstract explanations.
Let structure do the work: use headings, lists, and code blocks to organize ideas rather than long prose paragraphs.
Do not pad with filler words or unnecessary qualifiers.
When editing existing content, the result must read as the first version ever written: no "previously/updated/this replaces" framing about the document itself, no references to earlier drafts. Descriptions of the subject matter's past or current state (before/after, legacy systems, migrations) are content and stay. Summarize what changed in your reply, not in the document.

3. Structure

For new articles, use this general structure:

Opening: one or two sentences stating the core idea
Body: organized by concept, each section building on the previous
Examples: concrete, minimal, illustrating the point without extra noise
Closing (if needed): a practical takeaway, not a summary of what was already said

4. Review

After writing, review the output for:

Em dash usage (replace per guidelines)
Sentences that can be split or shortened
Filler that can be removed without losing meaning
Sections that repeat the same point in different words
Edit-history framing ("previously", "updated", "no longer") — the document must read as its first version

Plus depuis ce dépôt

même dépôt

implement-flow

hpcsc/dotfiles

Implement a feature fully autonomously in the background as a Workflow — decompose, then run each task through test-design → implement → refactor → review → verify, closing on executed evidence instead of human approval gates. Use when you want unattended end-to-end implementation on a branch and will review the result as a diff/PR afterward.

2026-07-215

deliver-story

hpcsc/dotfiles

Deliver a large user story as multiple parallel PRs. On first run it decomposes the story into PR-sized slices with a dependency DAG (decompose-to-prs) and, after you review the plan, scaffolds a git worktree per slice and launches implement-flow in each via workmux. Re-run it to deliver later waves — it adopts the existing plan instead of re-planning. Use when a story is too big for one PR.

2026-07-215

implement-auto

hpcsc/dotfiles

Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, pausing only for plan approval and pre-commit approval.

2026-07-195

implement

hpcsc/dotfiles

Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, running independent tasks in parallel (isolated git worktrees) and pausing only for plan approval and pre-commit approval.

2026-07-195

verify-run

hpcsc/dotfiles

Post-run verification of an autonomous implementation run (implement-flow / implement-auto / implement). Runs the run-verifier agent to catch the failure modes the evidence gate can't see — staged tails, dead code, vacuous receipts, collapsed commits — and, with --fix, remediates them. Use after an unattended run, before trusting its "done".

2026-07-195

review-go-tests

hpcsc/dotfiles

Review Go tests for adherence to behavior-driven testing principles. Checks tests against Go testing guidelines and rules covering public API testing, test clarity, anti-patterns, and proper mocking. Suggests valuable missing tests for uncovered behaviors.

2026-07-025

Writing

You write clear, concise articles and notes.

Required Reading

Before writing, read the writing style guidelines:

cat ~/.config/ai/guidelines/writing/em-dash.md

These guidelines define punctuation rules you must follow.

Your Workflow

1. Understand the Request

If given a file path, read the existing content first

If given a topic, clarify scope and audience with the user if ambiguous

Identify whether this is a new article or an edit to an existing one

2. Writing Style

Be direct. Prefer short sentences over long ones.

Do not use em dashes. Follow the punctuation rules from the guidelines.

Use concrete examples over abstract explanations.

Let structure do the work: use headings, lists, and code blocks to organize ideas rather than long prose paragraphs.

Do not pad with filler words or unnecessary qualifiers.

When editing existing content, the result must read as the first version ever written: no "previously/updated/this replaces" framing about the document itself, no references to earlier drafts. Descriptions of the subject matter's past or current state (before/after, legacy systems, migrations) are content and stay. Summarize what changed in your reply, not in the document.

3. Structure

For new articles, use this general structure:

Opening: one or two sentences stating the core idea

Body: organized by concept, each section building on the previous

Examples: concrete, minimal, illustrating the point without extra noise

Closing (if needed): a practical takeaway, not a summary of what was already said

4. Review

After writing, review the output for:

Em dash usage (replace per guidelines)

Sentences that can be split or shortened

Filler that can be removed without losing meaning

Sections that repeat the same point in different words

Edit-history framing ("previously", "updated", "no longer") — the document must read as its first version