vstorm-co
- 178 skills
- 0 followers
- 1.1k repo stars
- 5 days ago last updated
- ▌ Agent Testing · vstorm-coTry an agent before publishing it - the questions to ask, the failures to look for, what to change.
- ▌ Virtual Tables · vstorm-coDesign and use AgenticOS typed tables for an automation's records, state, notes and reporting.
- ▌ Agenticos Guide · vstorm-co bundleAnswer questions about AgenticOS itself - what a feature is called, how it works, how to connect it to Claude Code or another tool, the API - from the product's own documentation, not from a web search.
- ▌ Workflow Builder · vstorm-coBuild and verify AgenticOS automations and API integrations, including tools unavailable in the MCP gallery.
- ▌ Agent Instructions · vstorm-coWrite an agent's instructions so it does one job well - role, scope, refusals, sources and tone.
- ▌ Pydantic AI Import · vstorm-coBring an agent written with Pydantic AI into AgenticOS - read its code, map it to a draft, say what did not translate.
- ▌ Resolve Changelog Conflict · vstorm-coResolve a merge conflict in CHANGELOG.md by detecting the file's own convention (Keep a Changelog per-version sections, monthly sections, a single [Unreleased] bucket, or another format) and folding the other side's entries into it. Use whenever git reports a conflict in CHANGELOG.md, or when entries in an older format need folding into the current one.
- ▌ Deck Review · vstorm-coCheck a finished deck before it is shared - whether the titles tell the story, whether every number has a source, whether it is readable from the back of a room, and whether the ask is clear.
- ▌ Durable Work · vstorm-coCarry a large job through planning, specialists, coding tools, background topics and durable Tasks without losing decisions or claiming unfinished work is done. Use for long implementation, multi-stage research and work continued across chats.
- ▌ Visual Design · vstorm-co bundleDesign a clear interactive explanation, comparison, calculator or spatial view. Use for visual composition and quality judgment; exact rendering APIs come from the active tool.
- ▌ Artifact Pages · vstorm-co bundleDesign a useful published App or report for readers outside the chat. Use for information hierarchy, interaction and visual verification; the publishing tool owns its runtime contract.
- ▌ Deck Storyline · vstorm-coDecide what a presentation says before building slides - the audience and the decision, the one-sentence answer, a storyline of claims, and what goes in the notes.
- ▌ Platform Agents · vstorm-coBuild or repair an AgenticOS agent: choose capabilities and MCP tools, write its prompt, bind skills and knowledge, test failure cases and publish a verified version. Use for agent setup and configuration, not a one-off specialist.
- ▌ Platform Skills · vstorm-coCreate and improve reusable AgenticOS skills from a procedure or successful chat. Write accurate triggers, progressive references, acceptance cases and tool boundaries; save and bind the skill without confusing it with memory or permissions.
- ▌ Platform Tables · vstorm-coBuild useful AgenticOS tables with typed columns, rich-text notes, real user/agent references, views, default Kanban and conflict-safe writes. Reuse managed Task boards for TODOs and connect records to workflows and Apps.
- ▌ Platform Context · vstorm-coDecide what belongs in AgenticOS Context versus instructions, skills, memory, knowledge, Projects and Tasks. Design concise standing context, audience boundaries and a maintenance plan before attaching it to agents.
- ▌ Platform Workflows · vstorm-coDesign and verify AgenticOS workflow graphs, dependencies, bindings, entry points, API integrations and retries. Use for repeatable typed automation, including table events; discover node schemas before building.
- ▌ Presentation Decks · vstorm-co bundleBuild a readable HTML presentation with a claim-based storyline, appropriate slide density and working navigation. Use the selected tool and templates for implementation details.
- ▌ Document Production · vstorm-co bundleProduce polished papers, LaTeX documents, editable presentation files and exported reports with reproducible sources, correct citations, build checks and visual review. Choose files versus HTML Apps honestly; verify available compilers and renderers.
- ▌ Platform Automation · vstorm-coChoose and configure AgenticOS routines, watches, event triggers, task reminders and conversation suggestions without duplicating them. Explain schedules, working chats, Inbox cases and notification destinations.
- ▌ Research And Evidence · vstorm-coProduce a source-grounded research brief, comparison or paper: inspect primary evidence, dates and methods, reconcile contradictions, and preserve traceable claims for tables, decks and Apps.
- ▌ RAG Setup · vstorm-coChoose how documents become a knowledge base - parser, chunking, retrieval and reranking - for the documents at hand.
- ▌ Agent Design · vstorm-coTurn "I need an agent for X" into a design - its one job, what it may do, what it knows, who approves.
- ▌ Model Choice · vstorm-coPick a model for an agent by quality, speed, cost and where data may go - and say why.
- ▌ Agent Budgets · vstorm-coSet an agent's monthly budget and limits so a mistake costs little and a busy month does not stop it.
- ▌ Dev Agent · vstorm-coAI development agent. Opens a development branch and a stacked design branch up front, drives design and a general implementation plan to a reviewed, merged PR before any code exists, then — once merged — writes tests and the implementation on the development branch with review considered, without pushing. Portable across repos — detects the project's own test runner, source/test layout, branch naming and CI command rather than assuming one.
- ▌ Review Map · vstorm-coOn-demand visual walkthrough of a pull request for a reviewer — projects the diff onto the system architecture map (changed components highlighted, before/after flows, suggested reading order) and publishes it as a private HTML artifact. Use when a diff is too large or system-touching to hold in your head while reviewing.
- ▌ Pr Comments · vstorm-coUse this skill when user asks to address PR review comments. It will fetch all comments, present them in a structured format.
- ▌ Ste Writing · vstorm-coRewrite prose (docs, READMEs, PR descriptions, error messages, release notes, comments — never code) into ASD-STE100 Simplified Technical English. Use when asked to make writing not sound like AI, make docs clear or plain, enforce a controlled writing style, or write technical documentation that reads human. Two modes — strict (procedures/safety) and STE-flavored (general prose).
- ▌ Pr Description · vstorm-coCreate or update PR. Use this skill every time user asks to create or update a PR to ensure clear, consistent descriptions between PRs.
- ▌ Vstorm Code Review · vstorm-coHigh-signal, convergent code review for any repository. Runs a staged pipeline of subagents (Scope → Correctness → Security → Quality → Verification → Judge), one dedicated subagent per angle, all grading against one shared finding taxonomy, so every candidate is raised, filed, or refuted with proof — never silently re-surfaced after a fix. Accepts an optional `model` argument (default Claude Opus 4.8) that every subagent runs on. Use to review a pull request (first review) or to re-review code that was already reviewed and fixed. Run only after merge conflicts are resolved.
- ▌ Code Review 5 · vstorm-co bundleHow this organization reviews a change, and what a review must not let through.
- ▌ Channel Bot 2 · vstorm-coWork with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.
- ▌ RAG Knowledge 2 · vstorm-coWork with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vector_store }} + {{ cookiecutter.embedding_provider }} embeddings.
- ▌ Background Task 2 · vstorm-coAdd or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.background_tasks }}.
- ▌ Frontend Feature 2 · vstorm-coBuild a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
- ▌ Alembic Migration 2 · vstorm-coCreate, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Build And Compile 2 · vstorm-coBuilding, compiling, and resolving dependency issues across languages
- ▌
- ▌ Environment Discovery 2 · vstorm-coSystematic exploration of unknown environments before starting work
- ▌
- ▌
- ▌ Agent Tool · vstorm-coAdd a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.ai_framework }}.
- ▌ Pytest Suite · vstorm-coWrite or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
- ▌ Billing Stripe · vstorm-coWork with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.
- ▌ Production · vstorm-coMain orchestrator for the production-stack-skills pack. Routes /production subcommands to specialized skills. Use this skill when the user types /production followed by a subcommand (check, fastapi, postgres, docker, deploy, monitoring, security, errors, report, score). Also triggers when user says 'make this production ready', 'productionize this', or asks about production readiness in general.
- ▌ Production Check · vstorm-co bundleFull production readiness audit with 0-100 score — scans the entire project across security, error handling, observability, deployment readiness, database patterns, and container hygiene. Launches parallel analysis, classifies findings by severity, and produces a prioritized action plan. Use this skill when user says /production check, /production score, asks 'is this production ready', 'audit this project', 'how production ready is this', or wants a comprehensive codebase health check.
- ▌ Production Deploy · vstorm-co bundlePre-deployment validation and release management — structured checklists for database migrations, environment variables, rollback plans, backward compatibility, and deployment strategies. Use this skill when the user mentions deploy, release, ship to prod, merge to main, CI/CD pipeline, or says /production deploy. Triggers on deployment-related discussions, release planning, or pre-release validation.
- ▌ Production Docker · vstorm-co bundleDocker production hardening — multi-stage builds, non-root users, distroless images, BuildKit secrets, layer optimization, security scanning, and compose best practices. Use this skill when the user is creating or modifying Dockerfiles, docker-compose files, .dockerignore, or containerizing applications. Triggers on any Dockerfile, docker-compose.yml, .dockerignore, or when user mentions Docker, containers, or images. Also trigger when user says /production docker.
- ▌ Production Review · vstorm-co bundleProduction-readiness code review that checks for security vulnerabilities, error handling, logging, configuration, performance, and operational concerns. Use this skill when the user asks for a code review, PR review, quality check, production readiness check, or says 'review this', 'is this production ready', 'check my code'. Also trigger when reviewing pull requests that touch backend services, APIs, or infrastructure code. Works with Python, Node.js, Go, and Java codebases.
- ▌ Production Fastapi · vstorm-co bundleProduction-grade FastAPI patterns — structured logging, health checks, graceful shutdown, middleware, Pydantic v2, async patterns, error handling, and security hardening. Use this skill when the user is building or modifying a FastAPI application, working with Pydantic models, configuring Starlette middleware, setting up Uvicorn/Gunicorn, or asks about FastAPI best practices. Triggers when importing fastapi, starlette, pydantic, or uvicorn. Also trigger when user says /production fastapi. DO NOT trigger for Django or Flask unless explicitly asked.
- ▌ Production Planner · vstorm-coArchitecture planning for production systems — guides system design with scalability, reliability, security, and operational concerns from day one. Use this skill when the user asks to plan architecture, design a system, plan a new service, discuss system design, or says 'plan this', 'how should I architect this', 'design the system for'. Triggers on architecture discussions, system design, API design, data modeling, and infrastructure planning.
- ▌ Production Postgres · vstorm-co bundlePostgreSQL production patterns — safe migrations, indexing strategies, connection pooling, schema design, and query optimization. Use this skill when the user is working with PostgreSQL, writing database migrations (Alembic, Django migrations, raw SQL), designing database schemas, optimizing queries, setting up connection pooling (PgBouncer, asyncpg), or asks about database best practices. Triggers on SQL files, migration files, SQLAlchemy models, Django models, or Prisma schemas that target PostgreSQL.
- ▌ Production Security · vstorm-co bundleProduction security hardening — secrets management, CORS policy, authentication patterns, authorization models, rate limiting, security headers, dependency scanning, and OWASP Top 10 awareness. Use this skill when the user works on authentication, authorization, secrets, CORS, rate limiting, security headers, or any security-adjacent code. Also trigger when user says /production security.
- ▌ Production Monitoring · vstorm-co bundleProduction observability — OpenTelemetry traces, structured logging, metrics, alerting, health endpoints, and SLO definition. Use this skill when the user mentions monitoring, observability, logging, metrics, traces, alerts, SLOs, or says /production monitoring. Triggers on observability discussions, OTEL setup, structured logging configuration, Prometheus/Grafana setup, or alerting rules.
- ▌ Production Error Handling · vstorm-co bundleProduction error handling patterns — error taxonomy, retry with exponential backoff, circuit breakers, graceful degradation, dead-letter queues, and structured error logging. Use this skill when the user writes error-prone code (external API calls, database operations, file I/O, network calls), implements retry logic, or asks about resilience patterns. Also trigger when user says /production errors.
- ▌ Content · vstorm-coContent studio with brand consistency. Use this skill whenever the user wants to create content — blog posts, social media (X/Twitter, LinkedIn, Reddit, HN), presentations (Slidev/Reveal/Spectacle), infographics, image prompts, video scripts (Remotion), editorial calendars, or content audits. Also triggers on brand setup, voice profiling, content repurposing, and content strategy. Covers any request involving writing, publishing, visual content creation, or content planning. Even if the user doesn't say "content" explicitly — if they're asking to write a blog post, create slides, draft a thread, plan a content calendar, or check content quality — use this skill.
- ▌ Content Blog · vstorm-co bundleLong-form blog post generation with brand voice integration and anti-slop enforcement. Use when user wants to write a blog post, article, tutorial, case study, opinion piece, deep dive, or listicle.
- ▌ Content Audit · vstorm-co bundleContent quality audit with anti-slop detection and brand consistency scoring. Use when user wants to check content quality, audit a draft, score content, verify brand consistency, detect AI-generated patterns, or run a quality check before publishing.
- ▌ Content Image · vstorm-co bundleImage prompt engineering for AI image generation models. Use when user wants to generate images, create image prompts, or optimize prompts for DALL-E, Midjourney, Stable Diffusion, or other image generation tools.
- ▌ Content Setup · vstorm-co bundleInteractive brand onboarding that creates the /brand/ directory with BRAND.md, VOICE.md, and VISUAL.md. Use when user runs /content setup, /content brand show, /content brand update, or /content voice. Also triggers when any content skill detects brand/ is missing.
- ▌ Content Video · vstorm-co bundleVideo script generation and Remotion composition scaffolding. Use when user wants to create video content, storyboards, Remotion scripts, social media shorts, explainer videos, or video scripts.
- ▌ Content Reddit · vstorm-co bundleSubreddit-aware post generation that matches community norms. Use when user wants to create a Reddit post or comment for any subreddit.
- ▌ Content Twitter · vstorm-co bundleX/Twitter thread and single tweet generation with brand voice and hook-first writing. Use when user wants to create a tweet, thread, X post, or Twitter content.
- ▌ Content Calendar · vstorm-co bundleEditorial calendar planning and content scheduling. Use when user wants to plan a content calendar, create a publishing schedule, organize content across platforms, or plan a content series.
- ▌ Content Linkedin · vstorm-co bundleLinkedIn post generation with professional brand voice adaptation. Use when user wants to create a LinkedIn post, professional update, or LinkedIn content.
- ▌ Content Strategy · vstorm-co bundleContent strategy, ideation, positioning, and editorial direction. Use when user wants to plan content strategy, generate content ideas, define content pillars, create a content brief, or develop editorial positioning.
- ▌ Content Repurpose · vstorm-co bundleTransform content from one format into multiple formats while maintaining brand consistency. Use when user wants to repurpose content, convert a blog post to tweets, turn a presentation into a blog, create multiple formats from one piece, or cross-post content.
- ▌ Content Hackernews · vstorm-co bundleHacker News post generation for Show HN, Ask HN, and submissions. Use when user wants to post to Hacker News or write a Show HN/Ask HN post.
- ▌ Content Infographic · vstorm-co bundleGenerate SVG and HTML infographics with brand-aware design. Use when user wants to create an infographic, data visualization, process flow, comparison chart, stat card, or visual data summary.
- ▌ Content Presentation · vstorm-co bundleGenerate full HTML presentations using Slidev, Reveal.js, Spectacle, or raw HTML with brand integration. Use when user wants to create a presentation, slide deck, pitch deck, conference talk, workshop materials, keynote, sales deck, or client proposal slides. Even if user just says "slides" or "deck", use this skill.
- ▌ E2e Tests · vstorm-coWrite or fix a Playwright end-to-end test in frontend/e2e — a new journey spec, a seeded fixture, or debugging "the e2e suite passes but the feature is broken" / "make test-e2e fails". Use for any spec that crosses the whole stack (sign in, build an agent, publish, run, approve). Every page in this product renders its empty state when a query fails, so a spec that asserts on chrome is a spec that asserts on nothing.
- ▌ Agent Spec · vstorm-coChange the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
- ▌ Channel Bot · vstorm-coWork with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
- ▌ Project Docs · vstorm-coWrite or fix the documentation site — add a page, update one after a behaviour change, fix a dead link or a failing docs build, add a diagram or an icon, or wire a new page into the nav. Use whenever docs/ or mkdocs.yml is touched, and whenever a code change alters behaviour a page describes. make docs-build runs --strict, so a dead link fails CI.
- ▌ Backend Tests · vstorm-co bundleWrite or extend the backend Python test suite — a unit test for a service, an integration test against a real Postgres, an API test through the FastAPI app, or the test a bug fix needs. Also for "coverage is failing", "make test is red", and deciding which of the four layers a test belongs in. Uses anyio (not pytest-asyncio) and a 100% coverage gate on the platform layer.
- ▌ RAG Knowledge · vstorm-coWork with the knowledge base — ingest documents, run semantic search, manage collections, add a sync connector (Google Drive, S3), change a parser or an ingestion setting. Use when populating or debugging retrieval, when a document upload fails or dies silently in a worker, or when "the agent cannot find something that is definitely in the collection". pgvector + per-organization embedding keys.
- ▌ Vault Secrets · vstorm-coStore, read or rotate a credential — a provider API key, a channel bot token, an MCP token, a third-party service key — or add a new secret kind. Use whenever a change touches a credential at rest, whenever something needs to be encrypted, and whenever reviewing code that could leak a plaintext key into a response, a log line or an audit entry. Everything seals through app/core/vault.py; there is deliberately no second mechanism.
- ▌ Background Task · vstorm-coAdd or change work that runs outside the request/response cycle — document ingestion, MCP refresh, reports, cleanups, scheduled jobs — or debug a task that vanished with nothing in the logs. Use when something is slow or fire-and-forget, when adding a periodic job, and before reaching for asyncio.create_task (which drops work silently in this codebase's exact failure mode).
- ▌ MCP Connections · vstorm-coWork with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.
- ▌ Agent Capability · vstorm-co bundleAdd or change what an agent can do — a new tool the model can call, a new capability (knowledge, web search, charts, a guardrail, a compaction strategy), a tool rename, or a per-tool approval gate. Use whenever the ask is "give the agent a new tool/function/action", "add a capability", "let the agent do X". There is no @agent.tool and no assistant module in this project; every tool arrives through the capability registry.
- ▌ Frontend Feature · vstorm-coBuild or change a page, view or data-driven feature in the Next.js frontend — a route under the dashboard, wiring UI to a backend endpoint, a Zustand store, a permission that must hide a control, or localized copy. Use for any work in frontend/src, including "the page renders but shows an empty state" and "this button should not be visible to a Viewer".
- ▌ Permissions Rbac · vstorm-co bundleGate a route or a service on who may do it — add a permission, wire a role, decide between require() and resolve_access, share a resource with a grant, or debug "this user can see something they should not" and "a Viewer with an edit grant is being refused". Use for any authorization work, any new org-scoped route, and any review of one. There is no UserRole, RoleChecker or CurrentAdmin in this project.
- ▌ Alembic Migration · vstorm-coChange the PostgreSQL schema with Alembic — add or alter a table, column, index or constraint, backfill data, or tighten a rule on a column that already holds rows. Use whenever a SQLAlchemy model changes, and whenever a validation rule narrows on a field stored as JSON. A model change without a migration passes the unit suite (sessions are mocked) and breaks on real Postgres.
- ▌ Refund Policy · vstorm-co bundleWhen a refund is given without asking, when it needs approval, and how to say no.
- ▌ Incident Report · vstorm-co bundleHow to write up an incident so the next person can act on it, not just read it.
- ▌ Matter Intake · vstorm-coCapture a new matter completely, and run the conflict and scope questions first.
- ▌ API Support · vstorm-coAnswer integration questions with a request that works, and diagnose from status codes.
- ▌ Disclosure Triage · vstorm-coSort documents for relevance and privilege, and never decide privilege alone.
- ▌ Supplier Chase · vstorm-coDetect a late purchase order, chase it with the right ask, and escalate on a schedule.
- ▌ Bundle Preparation · vstorm-coAssemble and check a document bundle against the court's requirements.