How to use Aperio's memory tools well — when to recall, what is worth remembering, how to correct a wrong memory, and what must never be stored. Read this when connected to an Aperio MCP server; the tool schemas describe parameters, this describes judgment.
Use this skill to iteratively tune the keywords and descriptions of other SKILL.md files so the skill matcher fires the right skill for a prompt. Runs an autonomous mutate → score → keep/discard loop against a frozen eval set (exam §7 skill triggering), advancing a git branch when match accuracy improves. The eval and scorer are read-only ground truth; the curated keyword frontmatter of other skills is the only editable surface.
Use this skill before writing new code — when the ask is to add a helper, a small feature, a utility, or a new module, and the right amount of code has not been decided yet. Triggers: "write me a helper for…", "add a small feature", "do I need a library for this", "keep it minimal", weighing a new dependency, or any request that could be met by something that already exists. Walk the ladder first: reuse beats stdlib beats platform beats dependency beats new code. This is the pre-write sibling of code-simplification, which cleans up afterwards.
Use this skill when reading from or writing to the persistent memory store. Covers the memory tool API (recall, remember, update_memory, forget) and — for advanced direct access — the SQL schema, vector search patterns, and retrieval priority order against the Aperio Postgres store. Triggers: user states a preference, shares a fact or decision, gives a correction, asks the agent to remember something, or starts a task where past context would affect the output.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Toolkit for styling artifacts with a theme, and for creating distinctive, production-grade frontend interfaces. Use for: applying pre-set or custom themes to slides, docs, reports, HTML pages; building web components, pages, dashboards, React components, HTML/CSS layouts; or styling/beautifying any web UI with high design quality. ALWAYS use this skill before building any frontend or UI — it prevents the default "clean SaaS with purple gradient" trap that makes every AI-built site look identical.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Compact the current conversation into a handoff document a fresh agent can read to continue the work without re-deriving context. Use this when the context window is filling up, when the user says "handoff", "compact", "rotate context", "fresh agent", or "summarize for next session", or before a long-running task is paused. Pairs with `conversation-lifecycle` and `memory-protocol`.