AeyeOps

@aeyeops source repo

41 skills
0 followers
1 week ago last updated

▌
Cowork Migrate · aeyeops bundle
Use when moving, importing, copying, or migrating a Claude Cowork session, conversation, or project from one Windows machine to another, or when troubleshooting symptoms of a broken import like "session shows blank", "only the latest messages show", "scratchpad files don't open", "can't scroll past the last compaction", or "Loaded N messages (truncated via tail/compaction)" in the Cowork log. Delivers full history, working file links, and no truncated-transcript rendering bug, handling the undocumented two-layer compact_boundary truncation filter in app.asar that silently clips imported transcripts. Covers orphan sessions on Windows to Windows under the same Cowork account. Does not handle Cowork Spaces/Projects, Linux/macOS, or cross-account migration.

2 installs
▌
Opus Prompting · aeyeops bundle
Use when writing, reviewing, debugging, or rewriting instructions that Claude itself will read — CLAUDE.md files, skill files (SKILL.md, frontmatter descriptions), slash command templates (.claude/commands/*.md), and agent definitions (.claude/agents/*.md) — and when converting docs or runbooks into skills, drafting agent frontmatter from scratch, or asking what is "pulling weight" in a prompt. Symptoms it covers: an agent firing too often or on the wrong things, a prompt that is too long or full of MUST/NEVER/ALWAYS, Claude ignoring sections of a command, agents looping on tools instead of stopping, skills not activating, and descriptions that do not trigger correctly. Not for general code review, MCP server design, hook scripts, or API/SDK questions unless the artifact under discussion is a prompt Claude reads.

2 installs
▌
Markdown Mermaid · aeyeops bundle
Use when creating diagrams in Markdown files, debugging a "diagram not rendering" error, choosing a diagram type for documentation, visualizing a database schema or API flow, or fixing Mermaid syntax. Craft Mermaid flowcharts, ERDs, sequence diagrams, state machines, Gantt charts, and mindmaps with validated syntax templates, layout optimization, and cross-platform rendering notes for GitHub, GitLab, VS Code, and Obsidian.

2 installs
▌
Owasp Top 10 · aeyeops
Use when reviewing code for security, performing a security audit, checking for OWASP Top 10 vulnerabilities, fixing injection flaws, preventing XSS, securing authentication, or checking access control. Covers every category with detection patterns, vulnerable and fixed code examples, and prevention checklists - broken access control, cryptographic failures, injection including SQL and command injection, insecure design, security misconfiguration, vulnerable and outdated components, identification and authentication failures, software and data integrity failures, security logging and monitoring failures, and SSRF. For auditing existing code; for writing new code safely, use secure-coding.

2 installs
▌
Ultraplan Teams · aeyeops
Use when a multi-component project in Claude Code needs an agent team whose teammates message each other mid-task over a shared task list, rather than independent subagents: parallel workstreams with file-ownership boundaries, cross-cutting changes where one teammate's output unblocks another, or long builds coordinated with SendMessage. Extends ultraplan with Claude Code's teams feature; the coordinator plans in plan mode, gets approval, creates the team, and verifies. For independent subagents that report back, use ultraplan instead.

2 installs
▌
Ultrareview Fix · aeyeops
Use when working through the findings of a preceding ultrareview validation — systematically addressing the reported errors, alignment issues, gaps, and improvements by priority and applying each fix to the plan or the code. Trigger phrases include "ultrareview-fix", "fix the review findings", "address the ultrareview", and "apply those fixes". Expects an ultrareview summary in the conversation; the `ultrareview` skill produces it.

2 installs
▌
Architecture Docs · aeyeops bundle
Use when someone asks to document system architecture for a technical audience — write an ADR, capture an architectural decision, generate C4 diagrams (Context / Container / Component / Code), produce an OpenAPI spec for an HTTP API, draft a system or component design document, or document how services integrate. Covers the C4 model, Architectural Decision Records, OpenAPI specifications, and design documents for engineers who need to build against or reason about the architecture. Not for: end-user-facing docs (use the `aeo-docs:diataxis` skill instead — tutorials, how-tos, references, explanations live there), README content, or code-level inline documentation.

2 installs
▌
Secure Coding · aeyeops
Use when validating user input, handling a file upload, managing secrets, implementing authentication, handling authorization, encoding output, choosing cryptography, or applying secure defaults while writing code. Covers validation strategy and common validations, XSS prevention through output encoding and Content Security Policy, the secret storage hierarchy and what to do after a secret is exposed, password handling, JWT tokens and session management, role-based and resource-level access control, which cryptographic primitive to use when, and secure random number generation. For writing safe code; to audit existing code against the OWASP Top 10, use owasp-top-10.

2 installs
▌
Claude Agent Sdk · aeyeops bundle
Use when building autonomous AI agents in Python with the Claude Agent SDK — programmatic agents, tool chains, or multi-agent systems — and when deciding which SDK API or option a task needs. Covers the GTVR execution pattern (gather, take action, verify, repeat), the stateless query() and stateful ClaudeSDKClient APIs, streaming versus batch modes, custom tool creation with the @tool decorator, MCP server integration, hook-based execution control, permission boundaries, API key and OAuth token management, multi-agent coordination, and production deployment strategies. Not designed for basic chat interfaces.

2 installs
▌
Ultrareview Loop · aeyeops bundle
Use when a plan or a code change should go through a code review loop that keeps reviewing and fixing until no actionable findings remain: PR review before merge, plan review before implementation, or validation after a refactor. Runs /ultrareview, applies /ultrareview-fix to the findings, and re-reviews until the review passes or the iteration cap is reached. Unlike a single-pass reviewer, the loop closes its own findings. Usage: /ultrareview-loop [focus_area] [--max-iterations N].

2 installs
▌
Az CLI Operations · aeyeops bundle
Use when the user asks about Azure CLI commands, writing Azure CLI scripts, managing Azure resources, az login, az account, service principals, managed identity, or the credential chain; when driving VMs, Storage, VNets, NSGs, Key Vault, App Service, AKS, or RBAC from the command line; or when the question is JMESPath --query syntax, az graph query, CLI pagination, az wait, output formatting, multi-subscription work, resource locks, safe destructive commands, az rest API calls, az bicep, CLI extensions, cost management, cost analysis and spending, or az resource for services without a dedicated command. Covers the Azure CLI only, not the Azure SDKs or portal walkthroughs, and not AWS, which belongs to aws-cli-operations.

2 installs
▌
Agent Tui Expert · aeyeops bundle
Use when building a terminal user interface in Python - a Textual multi-pane dashboard, an IDE-style interface, a REPL shell, or an interactive line editor with completions and validation using Python Prompt Toolkit. Covers widget composition, containers, CSS styling, messages, key bindings, themes, command history, TUI testing with the Textual Pilot API and snapshot tests, MCP server access and sub-agent delegation from a TUI, version requirements, and WSL2 layout quirks. For full-screen Python terminal apps; for argument parsing and command-line UX, use python-cli-engineering.

2 installs
▌
D2 · aeyeops bundle
Use whenever the user wants to produce, edit, or render any kind of diagram with D2, the Terrastruct text-to-diagram language at https://d2lang.com — architecture, flowchart, sequence, ER/SQL schema, UML class, network topology, mind map, deployment, org chart, state machine, grid layout, mermaid-style flow, or anything similar — even when they don't say "D2" explicitly. Trigger on requests for `.d2` files, mentions of `d2`/`d2lang`, or open-ended diagramming tasks ("draw me a system diagram", "make a flowchart of X", "diagram the request flow", "give me an ER diagram for these tables"). Covers the full DSL — shapes, connections, containers, classes, vars, globs/filters, imports, layers/scenarios/steps, styling, themes, sketch mode, icons, markdown/LaTeX/code blocks, layout engines, CLI flags, and the specialized diagram shapes.

2 installs
▌
N8n · aeyeops bundle
Use when building, debugging, or reviewing n8n 2.x workflow automation: writing {{ }} expressions over $json, $node and $input; scripting a Code node in JavaScript or Python; node configuration and missing or unknown parameters; validation errors, warnings and false positives; driving the n8n-mcp MCP tools for node search, configuration validation and workflow creation; or choosing a workflow pattern for webhook processing, REST API integration, a database pipeline, an AI agent, or scheduled and cron automation. Covers the n8n workflow layer end to end — expression syntax, Code node APIs, node parameters, validation, MCP tooling and architectural workflow patterns — not self-hosted n8n installation, upgrades or infrastructure.

2 installs
▌
Diataxis · aeyeops bundle
Use whenever someone asks to document something for users — write a getting-started guide, generate an API, config, or CLI reference, write a deployment, migration, or troubleshooting guide, explain a design decision, or produce any docs that will live in `docs/`. Authors user-facing technical documentation following the Diataxis framework: tutorials, how-to guides, reference material, and conceptual explanations, each with its own structural template and no cross-mode bleed. Not for: README content, code comments, architecture / C4 / ADR / OpenAPI work (use `aeo-docs:architecture-docs` instead), or internal design docs that aren't user-facing.

2 installs
▌
Ultraplan · aeyeops bundle
Use when a multi-step task in Claude Code should be planned by a coordinator and implemented by parallel subagents: multi-agent planning for large refactors, multi-component features, or any work worth delegating to independent Opus subagents with a tracked task list. The coordinator enters plan mode, gets the breakdown approved, delegates each task, and verifies every result; subagents work independently and report back. When teammates must message each other mid-task, use ultraplan-teams instead.

2 installs
▌
Mlx Serving · aeyeops bundle
Use when the user asks about MLX serving, mlx_lm.server, oMLX, Apple Silicon LLM serving, or running a local LLM on a Mac, and when troubleshooting a model that fails to load, OOM during load or inference, a server that hangs or crashes at batch>1, tool calls returned as plaintext content, a throughput regression, or the choice between mlx-lm and oMLX. Also covers oMLX feature-flag tuning (turboquant_kv, dflash, MTP, specprefill, thinking_budget, max-concurrent-requests, force_sampling), the OptiQ proxy for models exceeding RAM, Llama-4 ChunkedKVCache batch handling, Llama-3 tool-call JSON format, and bench-driven validation of serving configs. Apple Silicon M-series only, not cloud LLM hosting, non-MLX backends such as llama.cpp, Ollama and vLLM, or model training.

2 installs
▌
Ultrareview · aeyeops
Use when validating a plan, code change, configuration, or any other work product before proceeding — checking the preceding context for errors, unvalidated assumptions, alignment issues, gaps, and improvement opportunities, and producing a machine-parseable summary of what it found. Trigger phrases include "ultrareview", "review this plan", "check my assumptions", "validate this before we build", and "what did we miss". Reports findings only; the companion `ultrareview-fix` skill applies them.

2 installs
▌
Nous Overview · aeyeops
Use when the user asks about nous, learnings, knowledge extraction, context injection, engram or cortex storage, how memory works, how learnings are captured, or how the self-improving context system works end to end. Explains the architecture - the SessionStart hook that injects prior learnings and knowledge, the Stop hook that watches context-window usage and spawns extraction workers, the statusline activity logger trigger, the learnings and knowledge lenses, per-project .claude/nous storage, context thresholds, and reconciliation. Orientation and data flow for the nous plugin, not a setup or command guide.

2 installs
▌
Repo Governance · aeyeops
Use when the user asks about repository documentation governance — AGENTS.md scaffolding, a repo bootstrap, a roadmap alignment review, a doc curation pass, sanitizing a repository before publishing, or which governance command to run next. Guides the `aeo-repo-*` command family and its lifecycle sequencing: bootstrap a scaffold, iterate with alignment reviews and curation passes, sanitize before publishing. Trigger phrases include "set up AGENTS.md", "curate the docs", "align the roadmap", and "is this repo safe to publish".

2 installs
▌
Glinet Slate7 · aeyeops bundle
Use when the user asks about the GL-iNet Slate 7 or GL-BE3600 travel router (Wi-Fi 7) - first connection and setup, admin panel access, VPN client or server configuration with WireGuard or OpenVPN (NordVPN, Mullvad, Surfshark and 30+ providers), AdGuard Home, Tor, Tailscale or ZeroTier, DDNS, network modes, SSH and CLI access, lost admin access, factory reset, firmware update, or U-Boot recovery of a bricked device. Also use when scripting the device through its JSON-RPC admin API at /rpc, provisioning the built-in WireGuard server without the UI (wg-server, add_peer, generate_peer), or configuring a Linux WireGuard client with an overlay VPN stacked on top of it. Applies to most GL-iNet sdk4 firmware devices, not to generic router questions.

2 installs
▌
Vscode Extension · aeyeops bundle
Use when building or debugging a VS Code extension on stable VS Code for Windows, macOS, or Linux desktop — scaffolding with esbuild, fixing blank webview panels or silent CSP violations, troubleshooting extensions that won't load after install with profiles, adding dual TreeView+WebviewView toggle panels, or publishing to the marketplace. Contains verified extension development workflows, webview CSP pitfall resolutions, and profile-based install fixes that produce more correct results than reasoning from general training alone. Do NOT use for code-insiders on WSL/Linux (use vscode-insiders-extension), VS Code user configuration (themes, keybindings, tasks.json), Chrome/browser extensions, Electron apps, JupyterLab plugins, or Monaco Editor embeds.

2 installs
▌
Tailscale Macos Headscale · aeyeops bundle
Use when adding a macOS host (macOS 26 Tahoe and later) to a self-hosted headscale mesh as a Tailscale client, or when Tailscale on macOS misbehaves: "failed to connect to local tailscale service", Tailscale.app stuck on "Starting...", `tailscale up` hanging on "joining", a blank menu-bar icon after install, or the Homebrew cask and formula fighting over the daemon. Covers the Homebrew Cask install, the NetworkExtension permission grants, `tailscale up --login-server` with a headscale preauth key, the deep-link fallback when the CLI cannot reach the daemon, headscale's numeric `--user` id pitfall, and reach verification. Not for official Tailscale onboarding, Linux or Windows clients, or headscale server install.

2 installs
▌
Red Green Refactor · aeyeops bundle
Use when practicing TDD: writing the failing test first, making it pass with the minimum code, refactoring under green, choosing between unit, integration, and end-to-end tests, or deciding how to build fixtures (inline, factory functions, shared pytest fixtures). Covers the red-green-refactor cycle with the mistakes at each phase, test-first case ordering, the transformation priority premise, Arrange-Act-Assert, fixture strategies, and test isolation, with Python examples.

2 installs
▌
Optimization Patterns · aeyeops
Use when optimizing performance, implementing caching, fixing N+1 queries, improving database queries, adding indexes, reducing latency, choosing a data structure, deciding whether to optimize at all, or reviewing code for performance anti-patterns. Covers caching strategies and the cache hierarchy, cache invalidation, the Python LRU cache and its pitfalls, N+1 detection and eager loading, index strategy, algorithmic complexity and Big-O tradeoffs, lazy loading, and connection pooling. Applies once a bottleneck is known; to find the bottleneck first, use profiling-guide.

2 installs
▌
Test Design Patterns · aeyeops bundle
Use when designing a test strategy or reviewing QA practice: deciding the test pyramid split between unit, integration, and end-to-end tests, fixing test anti-patterns (the liar, the giant, the mockery, the inspector, the flaky test), writing parameterized or table-driven tests, adding property-based tests, reading mutation testing results, or interpreting code coverage numbers. Python and pytest examples throughout.

2 installs
▌
MCP Architect Designer · aeyeops bundle
Use when architecting a Model Context Protocol (MCP) integration, building or deploying a custom MCP server, choosing a transport mechanism, or debugging protocol-level issues and connectivity failures. Covers the JSON-RPC 2.0 spec, the MCP protocol lifecycle, FastMCP framework patterns, dual-client authentication, deployment patterns, production hardening, and diagnostic techniques. Trigger phrases include "build an MCP server", "MCP server won't connect", "server disconnected", stdio versus streamable HTTP transport, and exposing tools, resources, or prompts to an MCP client.

2 installs
▌
Systematic Debugging · aeyeops bundle
Use when debugging a failure, reading a stack trace, reproducing a flaky or intermittent bug, isolating a regression, or running a root cause analysis. Hypothesis-driven debugging with a recorded experiment at every step: reproduce, read the whole error, form and test one hypothesis at a time, isolate by binary search over code and commits (git bisect), inputs, environment, and dependencies, then trace the root cause with 5 Whys and a fault tree. Also covers stack-trace anatomy, an error-pattern lookup table, and a debugger, profiler, and network tools reference.

2 installs
▌
Requirements Elicitation · aeyeops
Use when eliciting requirements, interviewing stakeholders, running a contextual inquiry or focus group, writing user stories, building a story map, prioritizing features, defining acceptance criteria, or building a requirements document. Covers structured interview and reverse-engineering techniques, functional and non-functional requirement types and constraints, MoSCoW, RICE, and Kano prioritization, story splitting patterns, Given-When-Then Gherkin, checklist and rule-based acceptance criteria, and requirements traceability. For discovery and specification; for the buy-or-build call, use build-vs-buy.

2 installs
▌
Automating Computer Use Testing · aeyeops bundle
Use when automating browser or UI testing with a computer-use model - generating Gemini 2.5 computer-use automation scripts, natural-language goal files, or Playwright-based test harnesses for web application QA. Covers requirements analysis, goal file generation and validation, harness script generation, test iteration, scenario generation, visual regression testing, form automation, decision trees for automation type and goal scope, and the templates, examples, and validator scripts that ship with the skill. For AI-driven browser interaction workflows, not for unit or API test suites.

2 installs
▌
Common Failure Patterns · aeyeops
Use when diagnosing a dependency conflict or version mismatch, a diamond dependency, an environment issue, a PATH problem, a permission error, an environment variable that is not taking effect, a CORS error, a DNS failure, a timeout, an async bug, a concurrency problem, a race condition, a deadlock, an unhandled promise rejection, or a memory leak. Every pattern is listed with its symptoms, causes, and fixes, so a recognized failure can be matched and closed quickly. A catalogue of known failures; for an unknown failure that needs a hypothesis-driven investigation, use systematic-debugging.

2 installs
▌
Aeo Skill Creator · aeyeops bundle
Use when creating a new skill from scratch, modifying or improving an existing skill, packaging one for distribution, or measuring skill performance — running evals to test a skill, benchmarking skill performance with variance analysis, or optimizing a skill's description for better triggering accuracy. Covers SKILL.md frontmatter, progressive disclosure, bundled references, scripts and assets, and the eval, benchmark, and description-optimization pipeline. Trigger phrases include "create a skill", "improve this skill", "run evals on my skill", and "why isn't my skill triggering".

2 installs
▌
AWS CLI Operations · aeyeops bundle
Use when the user asks about AWS CLI commands, writing AWS CLI scripts, querying AWS resources, managing AWS credentials, aws login, aws configure sso, assume role, or the credential chain; when driving S3, EC2, IAM, Lambda, VPC, RDS, DynamoDB, CloudWatch, or SSM from the command line; or when the question is JMESPath query syntax, --query versus --filters, CLI pagination, an aws cli waiter, output formatting, cross-account access, safe destructive commands, an S3 sync dry run, the aws cli pager blocking a script, or migrating from AWS CLI v1 to v2. Covers the AWS CLI v2 command surface only, not the AWS SDKs, not CloudFormation or Terraform authoring, and not Azure, which belongs to az-cli-operations.

2 installs
▌
Lima Vm Operations · aeyeops bundle
Use when the user asks about Lima, limactl, lima.yaml, lima start, or lima shell; wants to install Lima, configure or edit a Lima VM, create a Linux VM on a Mac, spin up an Ubuntu VM, run Docker on macOS, or run Linux on Apple Silicon. Also use for lima vmType vz, vz versus qemu, host.lima.internal, socket_vmnet, shared and bridged lima networking, virtiofs and 9p mounts, writable mounts, lima port forward, limactl edit, validate and template, Rosetta for running x86 binaries, and debugging a VM that will not start. Applies whenever Lima is mentioned even without an explicit request for help, because the vz-versus-qemu, mount-type, and network-mode choices are easy to get wrong. Apple Silicon Macs only.

2 installs
▌
Build Vs Buy · aeyeops
Use when evaluating build vs buy, comparing vendors, assessing a make or buy decision, analyzing total cost of ownership, evaluating SaaS against a custom build, or planning a vendor migration. Covers the decision framework, TCO models for both build and buy including upfront and ongoing costs, a vendor evaluation scorecard, feature-fit assessment, vendor due diligence, integration complexity and API evaluation, lock-in assessment, migration phases and a data migration checklist, and a decision document template. For the commercial decision; gathering the requirements themselves belongs to requirements-elicitation.

2 installs
▌
Profiling Guide · aeyeops
Use when profiling application performance, reading a flame graph, benchmarking code, identifying bottlenecks, measuring CPU usage, analyzing memory allocation, or profiling I/O and database queries. Covers profiling methodology, cProfile and how to interpret its output, py-spy sampling, line-level profiling, tracemalloc and memory_profiler, query and network I/O profiling, reading and generating flame graphs, microbenchmarking with timeit, load testing, and a decision tree for picking a profiler. Applies to measurement and diagnosis; to fix what the profile reveals, use optimization-patterns.

2 installs
▌
Slash Command Creator · aeyeops bundle
Use when authoring a custom Claude Code slash command, debugging slash command syntax, or converting a repetitive prompt into a reusable shortcut under `.claude/commands/`. Covers the reusable Markdown prompt template format, frontmatter configuration, argument handling, variable substitution, and workflow automation patterns. Trigger phrases include "create a slash command", "make a /command", "custom command", "argument-hint", and "my slash command does nothing".

2 installs
▌
React Pwa Designer · aeyeops bundle
Use when designing or building frontend interfaces in React: a progressive web app (PWA) that installs and works offline, a component-driven UI on shadcn/ui and Tailwind CSS, a responsive mobile-first layout, or a React component library. Covers frontend design through the SuperDesign workflow (layout, theme, animation, implementation), shadcn/ui component selection, service worker and manifest setup, PWA icon validation, state management choices, and WCAG AA accessibility. Uses the shadcn and context7 MCP servers when they are configured.

2 installs
▌
Vscode Insiders Extension · aeyeops bundle
Use when building or debugging a VS Code extension under WSL with code-insiders — scaffolding with esbuild, fixing blank webview panels or silent CSP violations, troubleshooting extensions that won't load after install with profiles, or publishing to the marketplace with code-insiders. Contains verified WSL-specific extension development workflows, webview CSP pitfall resolutions, and profile-based install fixes that produce more correct results than reasoning from general training alone. Targets code-insiders on WSL/Linux. Do NOT use for stable VS Code on Windows/macOS (use vscode-extension), VS Code user configuration (themes, keybindings, tasks.json), Chrome/browser extensions, Electron apps, JupyterLab plugins, or Monaco Editor embeds.

2 installs
▌
Python CLI Engineering · aeyeops bundle
Use when building or hardening a production-grade Python CLI tool, admin utility, data processor, or developer tooling - with UV for package management, Ruff for linting, Pyright for strict typing, Typer for commands, and Rich for polished output. Covers fail-fast patterns and custom exception hierarchies, modular code organization and module size limits, pydantic-settings configuration from YAML and .env, Makefile tasks and pre-commit checks, Rich progress bars, strict type-checking patterns, pytest structure for CLI commands, professional UX conventions, and building and installing the distribution. For command-line tools; for full-screen terminal UIs, use agent-tui-expert.

2 installs
▌
Python Data Engineering · aeyeops bundle
Use when implementing a data pipeline, ETL or ELT flow, or warehouse architecture in Python - SQLAlchemy 2.0 patterns such as TypeDecorator, hybrid properties and events, Pydantic integration, API-to-database flows, custom field schema evolution, incremental sync from an external system, or multi-source integration. Covers Kimball star schemas, medallion layers, slowly changing dimension handling, the dim_, fact_, and stg_ naming conventions, orchestration with dbt, Airflow, or Dagster, and testing a pipeline. Aimed at dimensional modeling with Python and PostgreSQL, not at BI tool configuration.

2 installs

41 published skills