# Is Writing

> Writing standard for IdeaSpaces Notes — structure, summaries, entities. Use when writing to the knowledge space.

- Skill: `ideaspaces-xyz/is-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ideaspaces-xyz/is-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ideaspaces-xyz/is-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: IdeaSpaces-xyz (https://skillmd.com/u/ideaspaces-xyz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ideaspaces-xyz/is-writing

---


# Writing Standard for IdeaSpaces

**The full standard lives in the [writing reference](../../reference/writing.md)** — generated from the canonical protocol skill catalog. Read it when writing or revising a Note: it covers summaries, sections as the semantic fingerprint, concreteness, progressive disclosure, and what not to do. The notes below are only the surface-specific bits.

## Frontmatter this surface writes

Required on create:
- `name` — human-readable title
- `summary` — the most important field. Dense, two sentences; it's what awareness and search surfaces show.

Optional but valuable:
- `tags` — descriptors for search, not categories ("regulatory", "series-a")
- `attached_to` — bind the entity a Note is about: `hostname:acme.com`, `person:alice`, `note:n_abc123`. Entities you name in the prose should be entities in the index — that's how Notes connect across the Space.

## Placement

Always inspect the target area first (`bash` with `find` / `rg --files`, then `read`). Understand what branches mean (their READMEs). Place content where it compounds with related knowledge; reuse existing locations before creating new ones.

This standard applies whenever **is-capture** proposes writing to the space.