djalmajr/skills
Manually write a durable page to an ai-memory instance via the MCP (memory_write_page) — for decisions, rules, gotchas, schemas/contracts, or operational constraints the user explicitly wants remembered.
npx skills add djalmajr/skills --skill aim-write
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Google Docs: Append text to a document.
44.6K installsDiátaxis Documentation Expert. An expert technical writer specializing in creating high-quality…
26.2K installsCLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, …
9.7K installsWrite a coding standards document for a project using the coding styles from the file(s) and/or…
9.6K installsCreate or refresh reviewer-facing PR titles and descriptions. Use when opening a PR, updating i…
3.9K installsWrite a feature spec or PRD from a problem statement or feature idea. Use when turning a vague …
3.1K installsOther skills from djalmajr/skills · top by installs.
npx skills add djalmajr/skills
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
2,763 B
SUMMARY.md
353 B
Persist a durable wiki page. Use only for canonical knowledge the user explicitly wants remembered — routine session notes are captured automatically by the hooks; do not hand-write those, and do not use a handoff for a permanent annotation.
configured, ask which endpoint to write to.
.ai-memory.toml; confirm if writingelsewhere.
kind is derived and recall stays clean:- decisions/ADR-NNNN-<slug>.md → decision - rules/<slug>.md → rule - gotchas/<slug>.md → gotcha - otherwise a topical path (e.g. runbooks/<slug>.md, <area>/<slug>.md). You can also set kind explicitly via frontmatter nodetype / the tool arg.
The rules/ prefix matters — use the underscore. Pages under rules/ (and pinned slots/) are ai-memory's highest-signal tier: they're surfaced verbatim in memorybriefing / memoryexplore / the dashboard, keyed by path GLOB 'rules/*'. A plain rules/ folder (no underscore) is just a normal page — it gets none of that and is only found by explicit query/read. So write durable rules to _rules/, never rules/.
Shared / cross-project rules (e.g. global agent conventions reused across every repo) belong in a dedicated scope — the reserved default/global scope — under rules/ there (write with scope: "global"). Recall is per-(workspace, project), so other projects reach them cross-scope via memoryquery scopes:[…] / memoryread_page (see aim-query), not automatically.
title, node_type, tags, optionalsource:). Link related pages with [[path.md]] (paths carry .md; links resolve by exact path). Never put live secrets/credentials in a page — redact (<see secret manager>).
memorywritepage (or the equivalent admin write) with workspace/project/path/body.aim-query for its topic).Keep pages focused and distilled — one fact/decision/gotcha per page reads and recalls best.