| Name | Contains | Score |
|---|---|---|
Demo plugin one for scope/agent install testing Contains: demo-skill-one Demo skill one used to verify global vs project install behavior across agents | SkillsRules | |
Demo plugin two for scope/agent install testing Contains: demo-skill-two Demo skill two used to verify global vs project install behavior across agents | SkillsRules | |
Rego is the declarative policy language used by Open Policy Agent (OPA). This tile covers writing and testing Rego policies for Kubernetes admission control, Terraform and infrastructure-as-code plan validation, Docker container authorization, HTTP API authorization, RBAC and role-based access control, data filtering, metadata annotations with opa inspect, and OPA policy testing with opa test. Contains: rego-domain-reference Reference material for writing Rego/OPA policies in a specific domain — Kubernetes admission control, Terraform/CloudFormation infrastructure-as-code validation, HTTP API authorization (request body validation, rate limiting), RBAC/ABAC access control models, metadata annotations, or Regal linter compliance by rule category. Load this when rules.md's general Rego style rules aren't enough and you need worked examples or domain-specific patterns for one of these areas. | SkillsRules | |
Read the house build's site camera and review source-cited construction payment proposals through protected owner callbacks and a host-owned append journal. Contains: construction-costs Add a payment row to the «Construction costs» sheet from a forwarded invoice, a construction wire/ACH notice or Baruch's own message. Use for "update Construction costs", "record this construction payment", "house build invoice" and "construction payment confirmation". Main only; Baruch approves each row on a Да/Нет card before it is written. construction-site Answer what is happening on the house build from the site camera's frames, and save a daily digest for the morning brief. Use for «чо там как на стройке», «что нового на стройке», «что было вчера на стройке», "what happened on site today", "is anyone on site" and "is the construction camera working". Reads camera frames only. Main only. | SkillsRules | |
v0.2.11 Finds open conference CFPs relevant to the user across Java/AI/developer conferences, with persistent sent/dismissed/remind state and source-aware Sessionize verification. NanoClaw per-chat overlay, loaded via containerConfig.additionalTiles. Contains: check-cfps Finds open CFPs relevant to Baruch across Java/AI/developer conferences and maintains persistent CFP state (sent/dismissed/remind) in cfp-state.json. Use when Baruch asks about upcoming conferences, call for papers, speaking opportunities, CFP deadlines, or where to submit a talk proposal. conference-followups Follow up with people Baruch met at a conference: from his list of names and conversation notes (text or voice), find each person's real address, draft one short email each in his voice, and post each as a one-tap «Отправить» card; offer a calendar hold only where a meeting was actually agreed. Use for "follow up with people I met", "conference contacts", or a post-event list. nightly-cfp-sync Cadence wrapper that runs check-cfps on its own schedule: refresh open CFP data, apply Sessionize verification, update cfp-state.json, emit an observable-silence cursor marker. Triggers: 'cfp sync', 'sync cfps', 'nightly cfp sync', 'refresh cfps nightly'. | SkillsRules | |
Hygiene patterns for any OpenCV + dlib vision pipeline: camera index probing + macOS init quirks, warmup that verifies real frames, frame-skip policy for expensive inference. Contains: camera-setup Open and warm up a cv2.VideoCapture reliably, probe for real (non-black) frames before starting the main loop, and handle macOS index enumeration quirks. Use when a VideoCapture call succeeds but returns black/stale frames, when switching between built-in and USB webcams, or when the first ~5 seconds of a pipeline produce zero face detections. frame-skip-policy Run expensive per-frame inference (face recognition, emotion classification, ViT embeddings) at a fraction of the capture rate so the camera loop stays responsive. Use when designing a vision pipeline that combines high-rate capture (30fps+) with heavy per-frame work (dlib, ViT, DeepFace) and you don't need every frame to be inferred. | SkillsRules | |
v0.1.1 now Contains: skill1 now summarize-v1 Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube). | SkillsRules | |
Spec-driven development on OpenSpec, with mechanical spec-as-source enforcement: a custom 'spec-as-source' OpenSpec schema adds file-ownership (targets) and test-verification ([@test]) metadata to every capability spec, three scripts (link check, ownership check, manifest build) keep code and specs from drifting apart, plus requirement-gathering, spec-writer, work-review, and a session-handoff skill with a proactive context-warning hook and a packaged handoff memory: the skill ships the exporter, importer, graph model, facts pipeline, Neo4j Compose runtime and operating guide to load handoffs into a local, authenticated Neo4j graph and query them. Contains: handoff Gestisce il sistema di passaggio di consegne tra sessioni AI per qualsiasi progetto. Crea, aggiorna e legge file HANDOFF-N.md nella cartella .handoff/ del progetto, mantenendo una knowledge base persistente con documentazione (CLAUDE.md, PROMPTS.md, CLIENTS.md, WORKFLOW.md). Usa questa skill ogni volta che l'utente vuole: - Salvare lo stato ("crea handoff", "salva lo stato", "facciamo il punto", "chiudiamo la sessione", "riprendiamo domani", "passaggio di consegne", "freeze the context", "save state") - Riprendere da una sessione precedente ("riprendi da dove eravamo", "carica handoff", "resume", "continua da HANDOFF", "cosa avevamo fatto") - Inizializzare la knowledge base di un nuovo progetto ("/handoff init") - Aggiornare la documentazione persistente (CLAUDE.md, PROMPTS.md, CLIENTS.md, WORKFLOW.md) Suggerisci proattivamente la creazione di un handoff dopo sessioni lunghe con modifiche importanti, debugging complessi, o decisioni architetturali significative. handoff-skill Traccia bug emersi testando una skill o un plugin, per guidarne l'upgrade. Controparte di handoff orientata al ciclo test → bug → fix di una skill specifica: crea/legge file BUG-N.md in `.handoffskill/<nome-skill>/` con uno STATUS.md aggregato. Usa quando l'utente segnala che una skill non funziona ("questo non funziona", "bug nella skill X"), vuole testarla sistematicamente ("testiamo la skill X"), o riprendere uno stato di test precedente ("riprendi i bug di X"). Invoca anche con "/handoff-skill". openspec-apply-change Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. openspec-archive-change Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. openspec-explore Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change. openspec-propose Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. openspec-sync-specs Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. plan-judge Reviews the entire PLAN.md of a new project through fixed, file-only provider rounds. Triggered by plan-mode when every plan entry is draft; Round 1 alternates Codex and Claude, then returns control to a human checkpoint. plan-mode Builds and maintains openspec/PLAN.md, the human-approved plan that sequences OpenSpec changes toward a stated goal — the tier above tasks.md. Explore read-only, draft entries, then stop and ask for approval; a change cannot start until its entry is approved. Trigger — make a plan, what should we build first, plan the work, roadmap, add this to the plan, approve the plan, why is the plan gate failing, NO-ENTRY, HASH-MISMATCH. prompt-engineer Rewrites a confirmed REFINED_PROMPT.md from prompt-loop into an ENGINEERED_PROMPT.md ready to execute: cleaned of reasoning-scripting and shouting, structured into the task contract (objective, context, scope, tools, action boundaries, verification, output, stop condition), every change traced to a numbered prompting rule, the lock register carried byte-identical, and an effort level recommended. Runs in a fresh-context subagent and never asks the user anything. Trigger — automatically after prompt-loop's output contract is confirmed and before openspec-propose, for non-trivial development work; explicitly on: engineer this prompt, ottimizza il prompt, prompt engineering, ingegnerizza il prompt, make this prompt executable. Do not use it on a prompt that has not been through prompt-loop: without a confirmed REFINED_PROMPT.md there is nothing to engineer. prompt-loop Refines an incoming prompt through a bounded score → interview → lock → rewrite loop until it is mechanically good enough (rubric score ≥ 9/10) to feed the SDD workflow. Trigger — automatically before openspec-propose when the request is non-trivial development work; explicitly on: refine this prompt, prompt loop, score my prompt, is this prompt ready. requirement-gathering Structured interview process that turns a vague stakeholder request into clear, actionable requirements before any spec or code is written. Trigger — new feature request, unclear requirements, vague task, clarify scope, before proposing a change. skill-router Single entry point to the spec-as-source workflow: given a request, decides which of the plugin's skills to activate — excluding trivial work first, deriving the current phase from the state of the repo second, and matching descriptions last — then runs the chosen skill inline or in a subagent. Use when you do not know which skill applies, or want the workflow driven for you. Trigger — which skill should I use, what do I do next, route this, start working on X, implement X, propose a change, continue the implementation, I want to build X, help me with this project, non so da dove partire. spec-as-source-setup Installs the spec-as-source OpenSpec schema, enforcement scripts, CI workflow, and pre-commit hooks into a project. Trigger — setup spec enforcement, add spec checks, configure spec-as-source, install spec scripts, add spec CI, install openspec schema. spec-ci-sync Syncs .github/workflows/spec-verification.yml with the test runner and test files declared in specs. Trigger — update CI workflow, sync spec CI, regenerate workflow, CI out of sync with specs, add spec test to CI. spec-loop Runs an autonomous Ralph-style loop over the tasks of an active OpenSpec change: one task per fresh-context agent invocation, mechanically gated by scripts/verify.sh, with runaway guardrails. Trigger — run the loop, ralph loop, autonomous apply, loop the tasks, implement the change unattended. spec-rebuild Deletes all files declared as targets in openspec/specs/**/spec.md and rebuilds them from the specs to verify spec-as-source integrity. Trigger — clean rebuild, verify source of truth, spec drift check, regenerate from specifications, rebuild from spec. spec-verify Runs all spec consistency checks (link integrity, target ownership, manifest build), the test suite, and a semantic drift spot-check, then reports results. Trigger — verify specs, spec check, run spec suite, check spec consistency, validate spec links, spec integrity, spec drift. spec-writer Creates and maintains capability spec.md files under openspec/specs/: requirements, scenarios, targets frontmatter, and Verified by test links. Trigger — write a spec, update a spec, document requirements, create capability spec, spec drift in frontmatter or links. work-review Reviews completed implementation requirement-by-requirement against its capability spec, with file:line evidence, before declaring work done. Trigger — review my work, is this done, verify completeness, check against spec before merging, final review. | SkillsRules | |
v1.1.12 Rules and skills that teach AI agents how to contribute to open source projects without being the villain. Contains: install-gate Scaffold the good-oss-citizen contribution gate into a consumer repository: a `pull_request_target` GitHub Actions check that fails any pull request whose description lacks a contribution declaration — an "AI Disclosure" section or an explicit "no AI assistance" statement — plus the vendored detection script, a PR template, and the tessl.json dependency entry. The gate enforces an outcome (AI use is disclosed) on the PR side, where it cannot be bypassed; it does not, and cannot, prove a tool ran. Use when a maintainer wants to add, install, set up, scaffold, enable, or wire up a contribution gate / a PR check that requires good-oss-citizen or AI-use disclosure before contributing. preflight Runs a structured 10-check pre-submission checklist against an open-source contribution before the contributor opens a pull request. Use when the user has written code for an open-source project and needs to prepare a PR, submit a contribution, or verify readiness. Triggers on "submit a PR", "open a pull request", "prepare the contribution", "ready to merge", "check my pull request". IMPORTANT — run this AFTER code is written but BEFORE submission. Checks: AI policy compliance and disclosure (including voluntary disclosure when no policy exists), diff size and focus, PR template, code style, commit conventions, tests, changelog and metadata, legal requirements (DCO/CLA), agent artifacts, slop detector patterns, and human ownership verification. propose Analyzes project contribution guidelines, identifies the right venue (pull request, issue, discussion, RFC/KEP/DEP), checks issue metadata (claims, assignments, labels), searches for prior rejected attempts, and drafts proposals formatted to project templates. Use when the user wants to contribute to an open-source project, fix a bug, submit a PR, improve or refactor code, asks where to submit a change, or needs help choosing between PR/issue/discussion/RFC. Triggers on "fix this issue", "submit a PR", "refactor this", "improve this code", "open a pull request". IMPORTANT — run this AFTER recon and BEFORE writing code to verify the right venue and check for prior attempts. recon Analyze an open source project's contribution norms, AI policy, conventions, and recent PR history before writing any code. Use when the user wants to contribute to an open source or GitHub project, fix a bug, submit a pull request, open a PR, make a contribution, or asks about contribution guidelines. Triggers on phrases like "fix this bug", "submit a PR", "contribute a fix", "open a pull request", "help me contribute", "how do I contribute", "what are the rules for this OSS project". IMPORTANT — run this BEFORE writing any code for an open source project. triage Check an already-open issue or pull request body against the host repo templates and draft a suggested comment for human review, not posting. Use when asked to triage an existing issue/PR, decide whether an existing body is good enough before responding, review whether it follows the repo template, or draft a comment asking for missing information. Triggers include "triage this issue", "review this existing PR", "does this PR follow the template", "check whether the PR body follows the repository's pull request template", "check whether the issue body follows the repository's issue template", "quick check on this open issue", "body is good enough", "asked for anything more before I respond", and "what's missing from this PR body". For NEW issue/PR drafts use `propose`; for own PR pre-submission verification use `preflight`. | SkillsRules | |
v0.22.7 Twelve skills for conference speakers covering rhetoric analysis, talk authoring, deck building and export, CFP submissions, publishing, illustrations, shownotes, screencast production, and vertical shorts, informed by a 113-entry Presentation Patterns taxonomy (83 observable: 64 patterns + 19 antipatterns; 30 unobservable: 21 patterns + 9 antipatterns). Contains: cfp-writer Write or adapt conference CFP submissions, talk titles, abstracts, takeaways, and speaker bios in the speaker's documented voice. Maintain the sessions catalog of approved submission materials. Use for CFPs, conference proposals, abstract revisions, and sessions-catalog reads or updates. illustrations Create deck illustrations, progressive-reveal image builds, and YouTube thumbnails. Establish a shared visual style, generate or edit slide art, and apply approved images to a deck. Use for illustration strategy, slide visuals, image fixes, build sequences, or standalone thumbnail requests. Talk authoring invokes strategy; presentation-builder invokes deck application. presentation-builder Build a PowerPoint or presenterm deck from an approved talk outline, edit an existing deck, or export slides to PDF. Use for slide construction, layout changes, deck edits, and standalone exports. New-talk argument and content development belongs to presentation-creator. presentation-creator Develop or adapt a speaker's talk from an idea through an approved outline, narrative, and speaker notes, grounded in their rhetoric vault. Use for new talks, audience adaptations, rhetorical architecture, outline revisions, and outline-schema repair. Coordinate deck building and publishing when requested. presentation-publisher Prepare an existing talk for delivery: curate resources, create or replace QR codes and short links, coordinate exports and shownotes, and run the speaker's publishing checklist. Use for QR requests, resource curation, go-live preparation, and full publishing workflows. Shownotes-only requests use shownotes-publisher; thumbnails use illustrations. screencast-editor Edit a talk-to-camera or demo screencast recorded in Camtasia for Mac (screen, camera and mic in one take) into a speaker-first video: plan cuts on sentence boundaries from Camtasia's own word timings, frame and zoom the screen evidence, audit the framing against the recorded pointer, generate the Camtasia project, correct the dynamic captions, time the YouTube chapters, and compose the thumbnail from frames of the take. Use when the user has a new Camtasia recording to edit, wants captions fixed, zooms adjusted, chapters or a description with time marks, or asks how to produce a screencast like a previous one. screencast-recorder Verify a recorded screen sequence against its approved storyboard: route and data revision, content framing and label readability, deliberate pans, the pointer landing on what it clicks, clip-to-clip continuity, and whether each visual proof occurs while its phrase is actually spoken. Use when checking a demo or screencast take before shipping it, when a recorded sequence must be proved rather than trusted, or when a clip join must be shown to be invisible. Verification only — this skill does not record. shorts-producer Turn a processed talk into vertical shorts: pick its most shareable takes from the finished vault analysis, then render each as a 1080x1920 video with the hook headline, the deck slide timed to the talk, a face-tracked crop of the speaker, a shownotes QR code, and live captions that highlight each word as it is spoken, lightly corrected while still matching the speech. Use when the user asks for shorts, reels, TikToks, vertical clips, social clips or viral moments from a talk, or wants captions fixed on one. shownotes-publisher Create and publish Jekyll shownotes pages and downloadable Agent Skills containing talk knowledge informed by rhetoric analysis. Use for "publish shownotes", "add talk to shownotes", "publish a skill for this talk", "update the talk skill", "add the video to shownotes", or speaking.jbaru.ch page updates. Supports pre-talk publishing from prepared notes and demos, post-event recordings, and skill refreshes. Encodes the custom shownotes parser's body format and single-file skill contract; creates the content, validates rendering and downloads, and publishes through the appropriate git flow. vault-clarification Runs interactive clarification sessions with the speaker after talk processing. Resolves ambiguities in rhetoric observations, validates findings, captures speaker intent, conducts humor post-mortems, and probes for blind-spot moments invisible to transcripts. Stores confirmed intents and infrastructure config in the tracking database. Opens with the topics vault-ingress recorded when the speaker accepted the session, and closes that session in the run obligations ledger. Triggers: "run clarification session", "humor post-mortem", "blind spot review", "capture speaker intent", "clarify rhetoric findings", "resume clarification session". vault-ingress Parses presentation talks to catalog rhetoric patterns: opening hooks, humor style, pacing, transitions, audience interaction, slide design, and verbal signatures. Downloads YouTube transcripts and analyzes slides (from PPTX, Google Drive PDFs, or video extraction), examining HOW the speaker presents. Processes talks in parallel batches and updates the rhetoric summary. Triggers: "parse my talks", "run the rhetoric analyzer", "analyze my presentation style", "how many talks have been processed", "update the rhetoric knowledge base", "check rhetoric vault status", "process remaining talks for style patterns". vault-profile Generates or updates the structured speaker-profile.json from vault data. Aggregates rhetoric summary, slide design spec, confirmed intents, and structured talk data into a machine-readable profile used by the presentation-creator skill. Also generates speaker achievement badges. Triggers: "generate speaker profile", "update speaker profile", "regenerate speaker profile", "sync speaker profile". | SkillsRules | |
v0.1.6 Ground truth for Govee Flow Plus Light Bars (H6056): phantom segments, bar-to-segment mapping, API auth and rate limits. Language-agnostic facts; Kotlin/Ktor reference example. Contains: govee-h6056-control Controls Govee H6056 Flow Plus light bars (smart LED lights) via cloud REST API with correct segment-to-bar mapping (Yankee=0-5, Golf=6-11), phantom-segment awareness (12-14 return 200 OK but do nothing), correct "off" semantics (rgb=(1,1,1), not (0,0,0)), and rate-limit guidance (~7 req/min sustained → pair with iot-actuator-patterns-kotlin debounce). Use when the user wants to control Govee H6056 light bars, change LED light colors or brightness, set bar segment colors, or automate Govee smart lighting scenes. | SkillsRules | |
Database architecture skills, docs, and rules for high-demand multi-tenant commerce platforms (PostgreSQL source of truth, Neo4j as derived GraphRAG projection, transactional outbox, RLS-based tenant isolation). Includes live schema introspection workflow via explicit Supabase MCP/read-only schema sources. Contains: adr-drafting Use when the user proposes — or the agent detects — a deviation from constitutional defaults that requires an Architecture Decision Record. Triggered by proposals to extract microservices, drop foreign keys, denormalize without measured evidence, store transactional truth in Neo4j, skip Row Level Security, skip the transactional outbox, run destructive migrations, use database-per-service, or any explicit override of a constitutional principle. Drafts a structured ADR with context, decision, consequences, alternatives rejected, migration path, validation criteria, and constitutional sections affected — and refuses to proceed with the underlying work until the ADR is at least Proposed status. commerce-database-architecture Use when designing or reviewing database architecture for high-demand multi-tenant commerce platforms — including PostgreSQL schema design, foreign keys, indexes, JSONB usage, multi-tenant isolation with Row Level Security, transactional outbox, Neo4j GraphRAG projections, event sourcing decisions, audit logging, partitioning, expand/contract migrations, and product/inventory/order modeling for restaurants, boutiques, drugstores, retailers, distributors, grocery, hardware, or appliance businesses. Triggered by any request to design tables, design schemas, create migrations, model products/variants/inventory/orders/payments, choose between monolith and microservices, choose between PostgreSQL and Neo4j as source of truth, model multi-tenant data, design event flows, or review an ER diagram. graph-rag-boundary-review Use when reviewing or designing how Neo4j and GraphRAG interact with PostgreSQL transactional truth — including any feature involving recommendations, semantic product search, ingredient relationships, substitution suggestions, complementary products, AI-assisted discovery, vector search combined with graph traversal, or any proposal that puts orders, inventory, payments, prices, or tenant access rules into Neo4j. Evaluates architectural proposals for data boundary violations, identifies sync pattern errors between Neo4j and PostgreSQL, produces structured design review feedback with severity-ranked findings, counter-proposals with Mermaid diagrams, eventing changes, and re-projection plans. Triggered by mentions of GraphRAG, Neo4j, knowledge graph, recommendations engine, semantic search, vector + graph hybrid search, AI product discovery, or any design that crosses the PostgreSQL ↔ Neo4j boundary. mermaid-diagram-review Use when the user shares a Mermaid ER diagram, schema sketch, or relationship diagram and asks for review, feedback, validation, or critique — including phrases like "what do you think of this", "look at this diagram", "I have this in mind", "can we model it like this", or pastes any block starting with "erDiagram" or "classDiagram". Validates the diagram against the constitution, returns a five-section structured response (constitutional violations, counter-proposal with improved Mermaid, migration plan if existing schema applies, test surface, open questions), and never silently accepts a design that violates tenant isolation, eventing, or graph-RAG boundaries. outbox-and-eventing-design Use when designing or reviewing the eventing layer of the commerce platform — including transactional outbox tables, outbox relays, domain event catalogs, idempotency keys, audit logs, memento snapshots, event sourcing decisions, and Neo4j projection workers. Triggered by requests to design events, design integration with external systems, design notification flows, design data sync to Neo4j or analytics warehouses, decide between event sourcing and CRUD, or review existing outbox / audit / event-sourcing schemas. postgres-schema-introspection Use when the agent needs to inspect the actual current state of a PostgreSQL database before answering a schema question — including before adding columns, before reviewing diagrams, before proposing migrations, or whenever the snapshot in .specify/memory/current-schema-state.md is stale. Connects via the configured Supabase MCP/read-only schema source, queries catalog metadata through list_tables or SELECT-only catalog SQL, and refreshes the snapshot file. Triggered by any "let me check what's already there", "what columns does X have", "what indexes exist on Y", "what does the schema look like", or by the snapshot being older than 24 hours. schema-evolution-workflow Use when the user wants to add an attribute, modify an entity, or model a new concept on top of an existing PostgreSQL schema — including phrases like "add a column to", "track this on the product", "we need to store", "model this concept", "extend the order with", "where should this live", or "should this be a new table". Inspects current state via the postgres-schema-introspection skill, runs a five-placement analysis (new column / JSONB key / EAV row / new related table / wrong entity), maps blast radius across foreign keys, outbox events, Neo4j projections, RLS, and indexes, and produces an expand/contract migration plan with rollback and tests. | SkillsDocsRules | |
v0.6.23 Skills and rules for the NanoClaw host agent (Claude Code on Mac), covering plugin promotion, container management, staging checks, repository safety, and upstream updates. Contains: add-ugos-project Register a new Docker Compose project on UGOS Pro (NASync) when the compose file lives in the nanoclaw repo. Plumbs the `/volume1/docker/PROJECT_NAME` directory symlink, the in-repo `.env` symlink, and the UGOS Pro SQLite registration row so the project appears in the Projects UI without UGOS rewriting the tracked compose file. Use when adding a new sidecar that needs UGOS Pro UI Start/Stop visibility, when wiring a repo-tracked compose project onto the NASync for the first time, when migrating an existing service to the symlinked-compose topology, or when asked to "register a UGOS project" / "add a sidecar to UGOS Pro". check-staging List pending skills and rules on the NAS staging area. Shows what the agent has created or updated that hasn't been promoted to plugins yet. Use before running promote, or when the user asks what's on staging. extract-to-overlay Sequential workflow for migrating an admin-plugin skill, rule, or script set into a per-chat overlay plugin. Audits cadence frontmatter, state-plane couplings, and cross-skill imports; moves files across two plugin repos; updates per-group additionalTiles config; ships each side through the publish pipeline; verifies live materialisation. Use when extracting an admin skill to an overlay, refactoring admin content into per-chat plugins, splitting capabilities out of nanoclaw-admin, or wiring additionalTiles for a freshly extracted overlay. host-contracts Resolve required NanoClaw host contracts, load operation constraints and identify exception checks before host work. Use for "deploy NanoClaw", "publish a plugin", "update image packages", "extract an overlay", "restore browser login", "enroll the private browser viewer", "relink WhatsApp", "recover a task", "check memory budgets", "read meeting chat evidence" or "capture Sessionize My Events" when a nanoclaw-host rule requires its full procedure. This skill reads the applicable policy; it does not deploy, operate services or grant approval. nuke Kill a running agent container on the NAS by Telegram group JID. The orchestrator respawns a fresh container on the next message. Does NOT delete registration or group folder. Use when a container is stuck, stale, or needs a fresh start. promote Promote agent-created skills and rules from NAS staging to plugin GitHub repos — opens a PR from staging, then hands the review, merge, and publish-confirmation lifecycle to the release skill. Use when there are new items on staging, after check-staging shows pending items, or when asked to deploy skills, push to production, or publish rules to a plugin repo. The promote scripts keep the historical `TILE_NAME` env var. reconcile Verify that all tessl plugins are in sync between git source, tessl registry, and the NAS orchestrator. Reports drift, unpublished content, untracked files, and version mismatches. Use when plugin state seems wrong, container behavior looks stale, you suspect out-of-sync plugins, or need to check plugin health before a release. Run after promoting skills or after any manual plugin edits. The script keeps its historical name, `./scripts/reconcile-tiles.sh`. ship-code Ship a committed code change to private NanoClaw (jbaruch/nanoclaw) through a reviewed PR, merge, and branch cleanup. Use when asked to ship a NanoClaw fix, open its PR, or merge its changes. Plugin repositories use the release skill directly. update-from-upstream Pull updates from qwibitai/nanoclaw directly into private NanoClaw through a reviewed PR, then deploy to NAS. Use when upstream has new features, when the user asks to update NanoClaw, or when /update-nanoclaw is invoked. | SkillsRules | |
v0.1.0 Enforces PKCE-based OAuth code flow replacing implicit auth flows for modern Supabase auth. Contains: pkce-auth-flow Generates code verifier/challenge pairs, exchanges authorization codes for sessions, sets secure HTTP-only session cookies, and configures server-side callback handling to implement the Proof Key for Code Exchange auth flow. Replaces implicit token-in-fragment flows by removing hash-based token extraction and localStorage usage. Use when implementing Supabase authentication, OAuth login, secure browser auth, SSR auth setup, or modern auth flow migration. | SkillsDocsRules | |
v0.3.15 Travel assistant for NanoClaw: byAir flight notifications (delay, gate, connection risk, inbound aircraft delay, time-to-leave, arrival logistics), traffic-aware drive planning for in-person meetings (auto drive blocks + leave-by traffic rechecks), travel-booking gap checks, and nightly TripIt sync. Per-chat overlay plugin. Contains: check-travel-bookings Checks upcoming trips for missing bookings (flights, hotels, accommodation) by reading the nightly-built `travel-db.json`, and warns when a hotel stay's TripIt location is a garbage value (a fee/rate note or blank) that needs a manual TripIt edit. Reports gaps for all upcoming trips — no date limit. Supports snooze state. Silent when all bookings are complete and every hotel location is a plausible address (or snoozed). Use when the user asks about upcoming travel plans, itinerary completeness, missing reservations, hotel address problems, or TripIt trip status. drive-engine The unified drive-block engine. Manages the travel-time / driving blocks on your primary calendar — drives to your flights, to your in-person meetings, and to a trip you drive to rather than fly. Use when the user asks about drive blocks, driving time, commute or travel-time blocks on their calendar, or drives to the airport, to a meeting, or to a hotel; when the operator replies to a drive notification to skip a meeting drive ('skip', 'skip 2 and 3'); when the operator says whether a trip is a drive or a flight ('drive', 'fly'); when the operator reports a drive block that looks wrong or missing; to configure EV stop-time planning from grounded vehicle/charging inputs; or to record confirmed conference-attendance day windows, grounded route addresses and exact venue labels from travel intake. Also runs on its own schedule. expertflyer Check seat availability or fare-class (upgrade) inventory on a flight, judge whether the seat already assigned is beaten by anything open, review seats across every upcoming flight at once, or create an ExpertFlyer alert. Actions - check fare-class/upgrade inventory (Z class, upgrade certificate, SkyTeam partner); check seats on one flight; judge a held seat against open inventory in its cabin and above; review upcoming flights for better seats; create a seat or fare-class alert; diagnose access. Use when the operator asks whether a seat is open, asks about Comfort+ / premium economy / business availability, asks whether their seat is the best available or worth changing, says check my upcoming flights for better seats, asks to be alerted when a seat or fare class opens up, or a new booking has just appeared. flight-assist Flight assist for tracked flights. Its precheck polls byAir every 2 minutes, sends templated flight notices (delay, gate change, cancellation, boarding, connection risk, inbound delay, time to leave, baggage carousel, day-before check, arrival logistics) through the host itself, and reconciles the managed calendar events. The model is never woken for a notice. Use to configure or diagnose the plugin — 'diagnose flight-assist', 'set flight-assist home base', 'configure flight-assist', 'why didn't I get a flight notice'. nightly-travel-sync Travel-data refresh bundle: TripIt → Reclaim timezone sync, refresh travel-schedule.json from the TripIt iCal feed with a two-tier Gmail freshness probe, rebuild travel-db.json, log newly-appeared trips to daily memory, then check upcoming trips for booking gaps. Runs daily; precheck-gated on travel-db.json freshness and schema currency. Triggers: 'sync trips', 'sync travel', 'update travel data', 'pull trip info', 'refresh travel schedule', 'rebuild travel db', 'check my bookings'. sync-tripit Adaptive scheduler for the TripIt/byAir refresh of active-flights.json. Precheck-gated to keep byAir polling responsive on flight days and idle between travel windows. Its precheck sends the sync's notices (tracked-flight changes, sync outage and recovery) through the host itself. Action: diagnose a failed precheck run. Use when active-flights.json isn't updating, byAir polling cadence isn't matching flight density, troubleshooting flight tracking / flight notifications / flight status updates / travel schedule refresh, or setting up flight-assist on a new install. The gate predicate and threshold constants live in skills/sync-tripit/precheck.py. travel-core Shared Python library for trip itineraries, planned positions, conference attendance windows, travel schedules, lodging, airport buffers, trip identity, home addresses and operator timezones in nanoclaw-travel. Flight-assist, drive-engine and travel-booking readers import these modules at runtime. Load when maintaining their shared travel-domain behavior; background library only, never invoke as a user workflow. | SkillsRules | |
v0.1.0 Age gate bypass test plugin | Rules | — |
v0.8.4 Agent-native E2E runtime with verifiable safety. 16 MCP tools including alethia_propose_tests (agent generates tests from a URL), alethia_assert_safety (proves destructive actions are blocked), and the expect block: NLP primitive unique to Alethia. Zero-IPC; 2-5x faster than Playwright MCP per flow; signed evidence packs. Works with Claude Code, Cursor, Cline. Contains: alethia Use when the user asks to run E2E tests, verify a web page, generate tests for an app, prove destructive actions are blocked, check if a UI element is visible, fill out a form, or drive a browser with natural language. Returns per-step results with safety classifications, policy decisions, DOM diffs, structured page context, and a signed audit trail. | SkillsDocsRules | |
Guardrails for Vue 2.7 + Vuetify 2.7 frontends built with Vite 7, with exact version pins, a working Vite and Axios setup, and Vuetify 2 component patterns that avoid Vue 3 and Vuetify 3 idioms. Contains: vue2-vuetify2-vite-setup Scaffolds and configures a Vue 2.7 + Vuetify 2.7 frontend built with Vite 7 and Axios, with pinned versions, the vite.config.js alias and dedupe for Vue, the main.js bootstrap with new Vue and new Vuetify, MDI icons, VITE_ environment variables and an axios API module. Use when creating a frontend with Vite for a project that requires Vue 2 or Vuetify 2, migrating a Vue 2 app from Vue CLI to Vite, adding or upgrading dependencies in a Vue 2 project, setting up ESLint for Vue 2, or fixing errors such as Multiple instances of Vue detected, Vuetify is not properly initialized, or an npm peer conflict on vite. vuetify2-components Builds Vue 2.7 + Vuetify 2 screens with the correct v2 props, slots and events and with Vue 2 reactivity, for example a point-of-sale screen with product search, a table of editable sale lines, a total, a confirmation dialog, forms and snackbars. Covers v-data-table headers and item slots, v-autocomplete with server search, v-dialog activators, v-form validation, v-snackbar, custom v-model with value and input, and array updates with splice or $set. Use when writing or reviewing .vue components in a Vue 2 or Vuetify 2 project, when a Vuetify prop or slot seems to do nothing, when a table does not update after a change, or when porting a Vue 3 or Vuetify 3 example to Vue 2. | SkillsRules | |
Standards and workflows for building secure, well-structured Terraform modules, including planning gates, validation steps, and implementation guidance. Contains: task-log-update Use when the user asks to log work, record what was done, or save task progress. Creates a structured markdown task log in `agent-logs/` with validation, waivers, and a final gates summary. task-workflow Use when the user asks you to implement a feature, fix a bug, or complete a repository task end-to-end (from scoping through code changes, validation, and final gate summary). terraform-plan Use when `.tf` or `.tfvars` files have been edited, added, or removed and you need to verify that the code changes produce the intended Terraform plan before the task is considered complete. Runs `terraform plan` in `examples/test_app` and cross-checks the result against the change set you expected your edits to cause. This is a gate: do not declare a Terraform task done without passing it. validation-runner Use when repository changes are complete and you need to run and report the required validation gates for the applicable change class (`docs-only`, `terraform-module`, `example-terraform`, `ci-workflow`, or `mixed`). | SkillsDocsRules | |
Meta-skill: how to pass skills/context to Claude sub-agents that start with fresh context, with documented SDK gotchas. Contains: delegate-to-sub-agent Orchestrate sub-agents across Claude Code AND GitHub Copilot. Covers what inherits vs what doesn't on each platform, how to pass skills explicitly, and the echo-skills validation handshake. Use when spawning child agents, delegating tasks, building multi-agent pipelines, or troubleshooting why a sub-agent doesn't have access to expected skills or context. | SkillsRules |
Can't find what you're looking for? Evaluate a missing skill.