@gallopsystems/agent-skills 1.0.0

package/README.md

@@ -0,0 +1,137 @@
+# Claude Skills
+
+A collection of Claude Code skills.
+
+## Installation
+
+First, add the marketplace:
+```
+/plugin marketplace add gallop-systems/claude-skills
+```
+
+Then install the skills you want:
+```
+/plugin install kysely-postgres@gallop-systems-claude-skills
+/plugin install nuxt-nitro-api@gallop-systems-claude-skills
+/plugin install nitro-testing@gallop-systems-claude-skills
+/plugin install linear@gallop-systems-claude-skills
+```
+
+## Updating
+
+Update a specific skill to the latest version:
+```
+/plugin update kysely-postgres@gallop-systems-claude-skills
+```
+
+**Auto-updates:** Third-party marketplaces don't auto-update by default. To enable:
+1. Run `/plugin` and select **Marketplaces**
+2. Choose `gallop-systems-claude-skills`
+3. Select **Enable auto-update**
+
+## Install as an npm dependency (per-repo)
+
+For JS/TS repos, you can pin the skills to a version via your lockfile instead of
+the marketplace. Add the package as a dev dependency:
+
+```
+yarn add -D @gallopsystems/agent-skills
+```
+
+On install, a `postinstall` script symlinks the package's content into the
+project's `.claude/` directory:
+
+- **skills** — each directory containing a `SKILL.md` → `.claude/skills/<name>`
+- **commands** — each `.md` file under any `commands/` directory → `.claude/commands/<name>.md`
+
+Updating is just a version bump:
+
+```
+yarn up @gallopsystems/agent-skills
+```
+
+These links are generated artifacts (they point into `node_modules` and are
+recreated on every install), so ignore them in `.gitignore`:
+
+```
+.claude/skills
+.claude/commands
+```
+
+Notes:
+- The script never clobbers a real `.claude/skills/<name>` or `.claude/commands/<name>`
+  you authored, and only removes symlinks it created. Run `yarn unlink-skills` to
+  remove all managed links.
+- Works out of the box with Yarn (Classic, or Berry with `nodeLinker: node-modules`)
+  and npm. **pnpm** (v10+) blocks dependency build scripts by default — add the
+  package to `pnpm.onlyBuiltDependencies` for the `postinstall` to run.
+- Yarn Berry with the default **PnP** linker is not supported (no `node_modules`
+  folder to link from); use `nodeLinker: node-modules`.
+
+## Available Skills
+
+### kysely-postgres
+
+Type-safe Kysely query patterns for PostgreSQL. Automatically activates when working in Node.js/TypeScript projects with Kysely.
+
+Covers:
+- Query patterns (SELECT, JOIN, WHERE, aggregations)
+- Migrations and recommended column types
+- JSON/JSONB and array handling
+- String concatenation
+- Common pitfalls to avoid
+
+### nuxt-nitro-api
+
+Nuxt 3 / Nitro API patterns for building type-safe full-stack applications. Automatically activates when working in Nuxt 3 projects.
+
+Covers:
+- Zod validation with h3 (Standard Schema support)
+- useFetch vs $fetch vs useAsyncData
+- Type inference (don't add manual types!)
+- nuxt-auth-utils (OAuth, WebAuthn, middleware)
+- Page structure (keep pages thin)
+- Composables vs utils
+- SSR + localStorage patterns
+- Deep linking (URL params sync)
+- Nitro tasks and job queues
+- Server-Sent Events (SSE)
+- Third-party service integrations
+
+### nitro-testing
+
+Test Nitro API handlers with real PostgreSQL using transaction rollback isolation. Each test runs in a transaction that auto-rolls back for complete isolation without cleanup overhead.
+
+Covers:
+- Transaction rollback pattern (fast, isolated, real SQL)
+- Vitest custom fixtures (`factories`, `db`)
+- Mock event helpers (`mockGet`, `mockPost`, `mockPatch`, `mockDelete`)
+- Factory pattern for test data creation
+- Global stubs for Nuxt auto-imports
+- Async/automation testing utilities
+- CI/CD setup with GitHub Actions and PostgreSQL
+
+## Adding New Skills
+
+1. Create a new plugin directory: `plugins/my-skill/`
+2. Add `plugins/my-skill/.claude-plugin/plugin.json`:
+   ```json
+   {
+     "name": "my-skill",
+     "description": "Short description",
+     "version": "1.0.0",
+     "author": { "name": "yeedle" }
+   }
+   ```
+3. Add `plugins/my-skill/skills/my-skill/SKILL.md` with frontmatter:
+   ```yaml
+   ---
+   name: my-skill
+   description: When to use this skill...
+   ---
+
+   # Skill content here
+   ```
+4. Add any reference files alongside `SKILL.md`
+5. Register the plugin in `.claude-plugin/marketplace.json`
+6. Commit and push

package/package.json

@@ -0,0 +1,26 @@
+{
+  "name": "@gallopsystems/agent-skills",
+  "version": "1.0.0",
+  "description": "Gallop Systems Claude Code skills, symlinked into .claude/skills on install.",
+  "license": "UNLICENSED",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/gallop-systems/claude-skills.git"
+  },
+  "files": [
+    "plugins",
+    "scripts/link-skills.mjs",
+    "README.md"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "postinstall": "node scripts/link-skills.mjs",
+    "link-skills": "node scripts/link-skills.mjs",
+    "unlink-skills": "node scripts/link-skills.mjs --unlink"
+  },
+  "engines": {
+    "node": ">=16"
+  }
+}

package/plugins/doctl/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "doctl",
+  "description": "Manage DigitalOcean App Platform deployments with the doctl CLI: auth contexts, listing apps, monitoring deployments, and checking logs.",
+  "version": "1.0.0",
+  "author": {
+    "name": "yeedle"
+  }
+}

package/plugins/doctl/skills/doctl/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: doctl
+description: Manage DigitalOcean App Platform deployments with doctl CLI. Covers auth contexts, listing apps, monitoring deployments, and checking logs.
+---
+
+# DigitalOcean doctl CLI Patterns
+
+This skill provides patterns for managing DigitalOcean resources via the `doctl` CLI, focused on App Platform.
+
+## When to Use This Skill
+
+Use this skill when:
+- Deploying or monitoring apps on DigitalOcean App Platform
+- Switching between DigitalOcean auth contexts
+- Checking deployment status or logs
+- Listing apps and their deployments
+
+## Auth Contexts
+
+doctl supports named auth contexts for managing multiple accounts/teams.
+
+```bash
+# Switch to a named context
+doctl auth switch --context <context-name>
+
+# List available contexts
+doctl auth list
+```
+
+Always switch context before running commands against a specific account.
+
+## App Platform
+
+### Listing Apps
+
+```bash
+# List all apps (shows ID, name, ingress URL, deployment status)
+doctl apps list
+```
+
+Key columns: `ID`, `Spec Name`, `Default Ingress`, `Active Deployment ID`, `In Progress Deployment ID`.
+
+The app ID is a UUID — you'll need it for all subsequent commands.
+
+### Monitoring Deployments
+
+```bash
+# List recent deployments for an app
+doctl apps list-deployments <app-id>
+```
+
+Key columns: `ID`, `Cause`, `Progress` (e.g. `6/6`), `Phase`.
+
+Deployment phases:
+- `PENDING_BUILD` — queued
+- `BUILDING` — build in progress
+- `DEPLOYING` — deploying built artifacts
+- `ACTIVE` — successfully deployed and serving traffic
+- `SUPERSEDED` — replaced by a newer deployment
+- `ERROR` — deployment failed
+
+The `Cause` column shows which commit triggered the deploy.
+
+### Deployment Logs
+
+```bash
+# Get build logs for a specific deployment
+doctl apps logs <app-id> --deployment <deployment-id> --type build
+
+# Get runtime logs
+doctl apps logs <app-id> --type run
+
+# Follow logs in real-time
+doctl apps logs <app-id> --type run --follow
+```
+
+Log types: `build`, `deploy`, `run`, `run_restarted`.
+
+### Getting App Details
+
+```bash
+# Get full app spec (useful for seeing components, env vars, routes)
+doctl apps get <app-id>
+
+# Get app spec as yaml
+doctl apps spec get <app-id>
+```
+
+## Common Gotchas
+
+- **Column names in `--format`**: doctl's `--format` flag is picky about column names. If you get `unknown column` errors, run the command without `--format` first to see available columns, then filter with standard tools like `head`.
+- **Deployment auto-trigger**: Apps connected to GitHub auto-deploy on push to the configured branch. No manual deploy needed unless auto-deploy is off.
+- **App ID vs Name**: Most commands require the app UUID, not the human-readable name. Get it from `doctl apps list`.

package/plugins/kysely-postgres/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "kysely-postgres",
+  "description": "Type-safe Kysely query patterns for PostgreSQL",
+  "version": "1.0.0",
+  "author": {
+    "name": "yeedle"
+  }
+}