npx skillsauth add classytic/arc --helpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Instructions for the agent to follow when this skill is activated.
Describe when this skill should be used.
tools
Audit a client codebase that has @classytic/arc installed for gaps in arc-convention adoption. Surfaces hand-rolled CRUD/auth/query/cache code that should be one defineResource() call, Mongoose models that should use @classytic/mongokit, manual JSON Schema that should be fieldRules, bypassed RequestScope, missing presets, and other patterns that defeat arc's "less code, more maintainability" promise. Produces a prioritized migration report with before/after recipes. Use when reviewing/auditing a downstream project that depends on @classytic/arc, when the user asks for an "arc audit", "arc gap analysis", "arc migration plan", "why isn't arc helping us", or when refactoring a Fastify/Express service to arc conventions. Triggers: arc audit, arc review, arc gap, arc migration, arc convention check, arc compliance, classytic audit, defineResource refactor, mongoose to mongokit, hand-rolled crud to arc, arc adoption, arc lint, arc smell, arc anti-pattern.
tools
@classytic/arc — Resource-oriented backend framework for Fastify. Use when building REST APIs with Fastify, resource CRUD, defineResource, createApp, permissions, presets, database adapters, hooks, events, QueryCache, authentication, multi-tenant SaaS, OpenAPI, job queues, WebSocket, MCP tools, or production deployment. Triggers: arc, fastify resource, defineResource, createApp, BaseController, arc preset, arc auth, arc events, arc jobs, arc websocket, arc mcp, arc plugin, arc testing, arc cli, arc permissions, arc hooks, arc factory, arc cache.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------