AGENT SKILL

writing-for-the-owner

How to write what the owner reads - Work titles and outcomes, resolutions, Attempt summaries, artifact and gate labels, and documents you share. Read before writing any of them in a session.

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 12
Forks
1

01 前言 Front Matter

name
writing-for-the-owner
description
How to write what the owner reads - Work titles and outcomes, resolutions, Attempt summaries, artifact and gate labels, and documents you share. Read before writing any of them in a session.

03 SKILL.md 正文

Some of what you write is rendered straight to the owner. Work titles and outcomes, Work resolutions, Attempt summaries, artifact labels and gate names all appear on the owner's Work surface exactly as you wrote them. The owner is not the actor that executes them.

Where a field is both an instruction to an actor and something the owner reads, write both, in that order, separated by a blank line:

  1. Open with one or two plain sentences a non-technical owner can read. Name what will exist when this is done and why it matters to the business. No file paths, flags, gate names, command names, ids, or internal vocabulary in that opening. Do not restate the title.
  2. Then the exact contract, unchanged. Every constraint, path, gate, banned value, source of evidence and honesty rule stays exactly as precise as it needs to be. The readable opening is an addition, never a replacement and never a softening: if making it read well would drop a requirement, keep the requirement and rewrite the sentence.

A wall of imperative instructions with no readable opening is the current failure. So is an opening that sells the work, invents significance the evidence does not support, or hides a constraint the executing actor needs.

Give artifacts and gates short names that say what they are, not what command produced them or every condition they satisfy. Use a recognisable noun phrase for the label (for example, “Homepage review” or “Browser check report”) and put purpose or qualification in the separate note. Do not reuse the full expected-artifact contract as a label. An owner scanning the evidence should be able to tell what each one is without opening it.

Assume the reader does not know the repository, toolchain or team shorthand. The opening must still make sense when read by itself. Use a concrete subject and active verb, one idea per sentence and familiar words. Expand an acronym the first time it matters. If the owner must translate a path, command, status token or agent role to learn what exists, the opening is not finished.

This is presentation of the same truth, not a second version of it. Never write an owner-facing opening that claims more than the contract below it delivers.

A document you share with a person or send for review must be finished work. Start with the content itself. Leave out Work ids, message numbers, Restless commands, company-computer paths and placeholders such as [LINK TO …]: say what a thing is in words, or link it. What changed and who changed it goes in the version note (document checkpoint --reason), which people see in the document's history, never at the top of the document. Restless checks this when you share or send for review and refuses a document that is not ready, saying what to fix.

Show a picture by embedding it: ![what it shows](/company/outputs/x.png), or in a document a path relative to it. PNG, JPEG, GIF and WebP show in place; convert anything else to PNG. A file:// link, localhost or a path outside /company cannot be shown.

A place you name (an address, a venue, a suburb) links to Google Maps, so the reader can see it: [Bondi Pavilion](https://www.google.com/maps/search/?api=1&query=Bondi%20Pavilion). On a page you build, follow the map pattern in the company-tools skill.

04 同仓库更多 Skills

BlueprintLabIO
BlueprintLabIO/restless-core

fixture-note-etiquette

How the company writes a Fixture Notes message. Used only by the connections smoke.

★ 12
BlueprintLabIO
BlueprintLabIO/restless-core

web-native-review

Prepare or independently review a rendered website against its outcome contract and a mature ground-truth reference. Use for landing pages, product sites, blogs, documentation sites, or other browser-native outcomes; do not use to judge source code alone or turn mechanical layout facts into a taste score.

★ 12
BlueprintLabIO
BlueprintLabIO/restless-core

scenario-evidence

Run a versioned Runtime scenario, probe its real capabilities, preserve compact evidence, and prepare its native review target. Use for a project outcome that benefits from repeatable setup/run/assertion/evidence—not to choose a plan, team, or business verdict.

★ 12
BlueprintLabIO
BlueprintLabIO/restless-core

research

Answer a question the company needs to decide on with a sourced brief - market facts, a technology, a regulation, an audience, a price, a supplier. Use when an answer must be found and checked on the web or in documents before acting; do not use for a quick lookup a single source settles, or for competitor landscapes (use competitor-research).

★ 12
BlueprintLabIO
BlueprintLabIO/restless-core

reference-led-reset

Reset a rejected or repeatedly drifting outcome into a genuinely fresh Work Attempt grounded in ordered authoritative references. Use when the owner asks to start over, when qualitative defects survive revision, or when a mechanically valid result conflicts with the product or brand source of truth. Do not use for an ordinary bounded repair that should preserve the current candidate.

★ 12
BlueprintLabIO
BlueprintLabIO/restless-core

publish-git

Safely reconcile, verify, and publish Git refs through the governed Restless effect path. Use for pushes or deployments driven by a Git push; do not use for read-only fetches, local Git work, or provider API administration.

★ 12