# Apex Notes Writing

> use skill when writing .md for Apex Notes; create/edit/import/delete/connect notes; enforce title/parent frontmatter, parent-only hierarchy, body wikilink refs, manifest sync.

- **Type:** Skill
- **Install:** `agentstack add skill-boriemannetje-apex-notes-apex-notes-writing`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [boriemannetje](https://agentstack.voostack.com/s/boriemannetje)
- **Installs:** 0
- **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [boriemannetje](https://github.com/boriemannetje)
- **Source:** https://github.com/boriemannetje/apex-notes/tree/main/skills/apex-notes-writing
- **Website:** https://apex-notes.netlify.app

## Install

```sh
agentstack add skill-boriemannetje-apex-notes-apex-notes-writing
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Apex Notes Writing

Use skill when writing/changing Apex Notes `.md`.

Repo rule: bundled `notes/` = neutral sample data only. No private/user notes in app repo.

## App Contract

- Workspace: app opens folder; if `notes/` exists, note root = `notes/`; else opened folder = note root.
- Reads `.md` recursively under note root; ignores dotfiles/symlinks.
- Source of truth after folder access = actual `.md`; `manifest.json` = seed/metadata path list.
- `layout.json` = graph positions keyed by note path; not hierarchy.
- New app-created workspace starts with empty `notes/manifest.json` + `notes/layout.json`.

## Frontmatter

Every note starts with only:

```yaml
---
title: "Human Readable Title"
parent: null
---
```

Rules:
- keys: only `title`, `parent`; no schema fields unless schema task.
- `title` = graph label; filename is storage.
- `parent: null` = loose note or independent root.
- `parent: "[[parent-stem]]"` = one immediate parent; depth is derived from the parent chain.
- Parent must exist, resolve uniquely, be outside child descendant chain.
- Multiple roots/loose notes in one folder are valid.
- Legacy `level` frontmatter is ignored by the app and may be removed when rewriting a note.

## Links

- Hierarchy edge: frontmatter `parent` only.
- Body `[[wikilink]]` = contextual/reference edge only.
- Body link forms: `[[stem]]`, `[[path/stem]]`, `[[Title]]`, `[[target|label]]`.
- Prefer parent/body refs by stable file stem; app also resolves path, title, slug.
- Do not body-link every ancestor; link only real context.
- Do not use body links to fake hierarchy.

## Files

- Preserve existing filenames unless rename requested.
- New filename: stable slug `.md`; unique; subfolders OK.
- Folder names never define hierarchy; `parent` does.
- Keep body concise; H1 matching title is OK, not hierarchy.
- Imports/pastes should choose/require parent when making connected children; otherwise use `parent: null`.

## Manifest/Layout

- On add/delete `.md`, update `manifest.json`.
- Manifest = sorted JSON array of `.md` paths relative to note root.
- Manifest lists Markdown only; no `layout.json`, media, dirs, non-md.
- If deleting/renaming and touching `layout.json`, remove/rename stale keys only; do not invent hierarchy there.
- Opened folders can still load files not in manifest, but seed preview needs manifest parity.

## Edits

- Before edit: read current note set + manifest; detect existing hierarchy.
- Connect/reparent: change only the child `parent`; descendants derive depth automatically.
- If an existing note has legacy `level`, remove it the next time you rewrite that note.
- Delete parent: children may keep broken parents unless user asks reparent.
- Avoid duplicate titles/aliases; duplicate aliases make refs ambiguous.
- Keep unknown/private content out of repo sample notes.

## Validate

Before done:
- all notes: frontmatter present; only 2 keys; title present.
- parents: null or exactly one `[[...]]`; resolves uniquely; no missing parent; no cycles.
- connected notes: every child has exactly one immediate parent.
- body links: references only; no hierarchy encoded in body text.
- manifest: missing/extra paths fixed; all paths `.md`, relative, sorted.
- layout: no stale path keys if edited.

Report compactly: `notes=N parentless=N connected=N manifest_missing=N manifest_extra=N fixes=[...]`.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [boriemannetje](https://github.com/boriemannetje)
- **Source:** [boriemannetje/apex-notes](https://github.com/boriemannetje/apex-notes)
- **License:** MIT
- **Homepage:** https://apex-notes.netlify.app

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-boriemannetje-apex-notes-apex-notes-writing
- Seller: https://agentstack.voostack.com/s/boriemannetje
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.