READY
Personal AI Assistant

CYRIX

Mark III. The third generation.

A personal executive assistant that plans, researches, writes, and remembers. Rebuilt from the ground up.

scroll

What is CYRIX

CYRIX is a personal executive assistant built on Claude Code by Anthropic. It is not a single chatbot. It is a wiki-LLM: a local knowledge vault, a set of skills, and isolated agents that work together on real tasks.

Everything CYRIX knows lives in a Markdown wiki. It reads only what a question needs, never the whole vault. New knowledge gets written back automatically, so every session builds on the last.

Mark III is a full rebuild. Two earlier versions taught the lessons; this one turned them into a system Nicky relies on every day to work faster and think clearer.

Wiki-LLM

Knowledge lives in a Markdown vault. Lazy lookup pulls in only the pages a question needs.

Architecture

Skills run the workflows. Agents do the heavy work in isolation. Memory carries across every session.

Self-maintaining

Sessions log themselves, knowledge is distilled back into the wiki, and audits keep it clean.

0
Active
Skills
0
Autonomous
Agents
0
Automation
Hooks
0
Knowledge
Wiki

What CYRIX Can Do

Six skills, each a Markdown instruction set that walks CYRIX through one workflow and hands the heavy lifting to an agent.

Web Research
/search

Searches the web through Tavily, with WebFetch and WebSearch as automatic fallbacks. One query, three layers of redundancy, so a lookup never dead-ends on a quota error.

Tavily Fallback chain CVE-ready
Doc Ingest
/ingest

Crawls a URL or raw text and turns it into a structured wiki reference: curated summaries, frontmatter, and a master index. Old versions get archived, never overwritten.

Multi-page crawl Frontmatter Supersession
Session Close
/einde-sessie

Closes a work session. It writes the session log, merges new insights into memory without blind-appending, and appends any decisions to the running log.

Session log Memory merge Decisions
Dutch Writer
/dutch-write

Rewrites Dutch text against the DutchQuill style rules. It strips AI tells and banned words, fixes grammar, and reports every change it made so nothing is silent.

DutchQuill Humanize NL
Cert Tracker
/cert

Runs a certification study session. Inbox notes and screenshots become structured module notes, and progress is updated across the roadmap. Built for the OSCP path.

Inbox → notes Progress OSCP path
Session Distill
/process-sessions

Hands raw session logs to the curator agent, which distills them into knowledge notes, decisions, and memory updates. Every bucket gets a dry-run preview before anything is written.

Distillation Per-bucket Dry-run

Work in Isolation

Three subagents handle the heavy, messy work in their own context, so the main conversation stays clean.

Security Reviewer
security-reviewer

A read-only secret scanner. It checks every edit for exposed API keys, private keys, real IPs, and client data, hard-blocking the obvious leaks and flagging the borderline ones.

Read-only Secret scan Pre-commit
Wiki Librarian
wiki-librarian

Audits the wiki on three cadences: daily, weekly, and monthly. It hunts broken links, orphan notes, missing frontmatter, and stale references, then writes findings you can act on.

3 cadences Link lint Orphans
Session Curator
session-curator

Reads a raw session log and sorts it into knowledge, decisions, project updates, and memory. Nothing gets written to the wiki until a dry-run preview is approved.

Distillation 5 buckets Dry-run

How It Works

You

Give CYRIX a task in plain language. A skill fires, either from a slash command or from describing what you need. It reads only the wiki pages that matter.

Skills

Skills are reusable Markdown instruction sets. They walk CYRIX through a workflow step by step, check in with you along the way, and hand the heavy work to agents.

Agents

Agents are autonomous workers. They take on the isolated, complex jobs, secret scans, wiki audits, log distillation, in their own context, so the main thread stays focused.

You → Skills → Agents → Wiki / Files / Git

// Memory and session pipeline

Hooks run the loop on their own. A session starts by loading memory and priorities, logs itself when it ends, and gets distilled back into the wiki. So every session builds on the last, without you lifting a finger.

Examples in Action

/ingest
"Ingest the Claude Code docs."
Doc Ingest

CYRIX maps the site, crawls every page, and writes curated summaries into the wiki with frontmatter and a master index. Each page gets a review date, and earlier versions move to the archive.

/einde-sessie
"End the session."
Session Close

CYRIX writes the session log, pulls the lasting insights into memory through a real merge rather than a blind append, and records any decisions in the log. The next session opens already knowing what happened.

/cert
"Study session for CPTS."
Cert Tracking

CYRIX reads the inbox notes and screenshots from the study session, turns them into structured module notes with commands and takeaways, and updates progress in the certification roadmap.

Built on Claude Code

Powered by Claude by Anthropic through the Claude Code CLI

Skills, agents, and knowledge are Markdown files: readable, auditable, version-controlled

No server. No database. Just Claude and a local Obsidian-compatible wiki.

Privacy-first: a public template where personal context stays gitignored and local

Claude Code Markdown-based Local-first Privacy-first
# CYRIX architecture

platform: Claude Code
skills: 6 active
agents: 3 autonomous
hooks: 5 automated
memory: persistent
wiki: lazy-lookup
storage: local filesystem
server: none
database: none
status: operational
Evolution

MK‑I → II → III
The Rebuild

Two earlier versions found the shape. Mark III tore it down and rebuilt it around a wiki-LLM core: lazy lookup, a self-running session pipeline, and agents that keep the whole thing clean.

The result is the system Nicky leans on every day. It plans, researches, writes, and remembers, and it cuts the busywork that used to slow each session down. That is what makes CYRIX worth the rebuild.

Architect

Nicky Jacobs

SOC Analyst · Aspiring Red Teamer

Built by Nicky Jacobs, a SOC Analyst on the OSCP path and the architect behind CYRIX. He uses it every day to plan, research, and write, and to keep three versions of lessons working for him instead of against him.