tezra-io

Use when the user asks what Fermix is, what it can do, or how its agent loop, providers, channels, jobs, memory, sandbox, built-ins, skills, plugins, and config/setup surfaces fit together.

Use when operating websites or local web apps through the built-in browser tool.

Inspect Google Calendar, check availability, and create, update, move, RSVP to, or delete events (with confirmation) through the Fermix Google Calendar plugin.

Search Google Drive and create folders, upload files, rename, move, or copy files through the Fermix Google Drive plugin.

Search, read, compose/send, draft, reply, label, and trash Gmail messages (confirming sends and trashing) through the Fermix Gmail plugin.

Grounded research on places, businesses, restaurants, hotels, people, products, events, travel and flights, and similar real-world subjects. Use whenever the answer should be cited, might have changed since training data, or needs to be verified against current sources rather than recalled from memory.

Implementation workflow for coding tasks. Iterates Linear issues by priority per project. Spawns Codex for TDD-style implementation, runs full gate, Claude review, fix loop, and ships on main. Use when the user says "build", "implement", "fix", or references a task to work on.

Architecture and design for new projects, major features, or significant changes. Use at project kickoff when the task involves new modules, multi-file changes, or architectural decisions. Produces an approved design doc, a CLAUDE.md, and creates Linear issues for implementation. Also use when someone asks to "design", "architect", or "plan" a feature, when writing a design doc, or when a task touches 4+ files or introduces a new subsystem. Applies to new features, feature upgrades, design changes, and architectural changes. Not needed for small bug fixes, single-file changes, or well-understood patterns under 3 files.

Build and maintain LLM-powered personal knowledge bases using Karpathy's Wiki pattern. Handles wiki initialization (directory structure, schema), source ingestion (articles, papers, notes into structured wiki pages), knowledge querying (synthesis with citations), and wiki health checks (lint for contradictions, orphans, gaps). Use this skill whenever the user mentions knowledge bases, research wikis, ingesting sources, research notes, adding articles or papers to a collection, synthesizing research, "add to wiki", "ingest this", wiki maintenance, or asks to organize/structure their knowledge on any topic. Also trigger when the user works in a directory containing a wiki/ and raw/ folder structure, or references index.md/log.md in a knowledge base context.

Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.

Interact with the Loomforge workflow engine for agentic software delivery. Use whenever the user wants to submit Linear issues for building, check build/run status, manage the build queue, troubleshoot failed or blocked runs, kick off a nightly build, or ship issues for a project. Also use for the design flow: scaffolding a new project from a rough requirement, drafting or extending a design doc, publishing to Linear, and registering the project for future builds. Also use when the user asks about Loomforge setup, daemon health, or project configuration. Loomforge handles both the pre-build design pipeline (scaffold → draft → review → publish) and the full execution lifecycle (Linear fetch, build, review, push, pull request creation, Linear status sync).