lylo
13 verified skills2,184 total stars
sentry
Investigate and fix a Sentry issue in this codebase. Use when the user provides a Sentry issue URL or ID and wants diagnosis, a fix, verification, or a PR.
development168
.claude/skills/r2
--- name: r2 description: Interact with Cloudflare R2 object storage - list objects, view stats, fetch files, and verify backup integrity. Usage: /r2 <command> [bucket] [args] allowed-tools: Bash --- # Cloudflare R2 Interact with Cloudflare R2 buckets via the Cloudflare API. ## Setup Read credentials from `.env`: ```bash grep '^CLOUDFLARE_' /Users/olly/dev/pagecord/.env ``` - **Account ID**: `CLOUDFLARE_ACCOUNT_ID` - **Bucket tokens**: `CLOUDFLARE_R2_{BUCKET_ENV}` or `CLOUDFLARE_R2_{BUCKET
tools168
.claude/skills/pagecord
--- name: pagecord description: Interact with the Pagecord API - list posts/pages, publish content, and manage blog resources. Usage: /pagecord <command> [args] allowed-tools: Bash, Read, Glob --- # Pagecord API Interact with Pagecord blogs via the REST API. ## Setup Read the API key from `.env`: ```bash grep '^PAGECORD' /Users/olly/dev/pagecord/.env ``` Look for `PAGECORD_API_KEY` for the default blog, or `PAGECORD_{BLOG}_API_KEY` for a specific blog (e.g. `PAGECORD_HELP_API_KEY` for the
tools168
ci
Run the CI pipeline locally (brakeman, rubocop, importmap audit, tests). Use when asked to run CI, check code quality, or verify code before pushing.
development168
.claude/skills/ui-review
# UI Review Skill When reviewing UI changes: 1. Check all state transitions (loading, sending, sent, error) 2. Verify data availability after redirects - are background jobs involved? 3. Confirm subscriber/record counts aren't read before async jobs complete 4. Test both happy path and edge cases for timing 5. Run the relevant system tests if they exist
testing168
support
Handle customer support emails - investigate issues and draft responses. Paste a customer email to get started.
data-ai168
.claude/skills/sentry
--- name: sentry description: Fix a Sentry error and create a PR. Usage: /sentry <issue-url-or-id> --- # Sentry Issue Fixer Automatically analyze a Sentry error, find the root cause, implement a fix, and create a PR. ## Input The user provides either: - A full Sentry issue URL (e.g., `https://sentry.io/organizations/pagecord/issues/123456/`) - A short issue ID (e.g., `PAGECORD-123`) If only an ID is provided, use organization slug `pagecord`. ## Steps ### 1. Get Issue Details Use the Sen
data-ai168
support
Investigate a customer support email and draft a reply. Use when the user pastes a customer message, bug report, billing question, feature request, or how-to question.
data-ai168
r2
Interact with Cloudflare R2 buckets used by Pagecord. Use when the user wants to list objects, inspect bucket stats, fetch files, or check backup integrity in R2.
testing168
ci
Run the local CI sequence for this repo. Use when the user asks to run CI, verify a branch before push, or check code quality with the full local pipeline.
development168
.claude/skills/fizzy
--- name: fizzy description: Interact with the Fizzy bug tracker - list, create, update, close cards, add comments, and more. Usage: /fizzy <action> [args] allowed-tools: Bash, Read, Grep --- # Fizzy Bug Tracker Interact with the Fizzy bug tracker via its API. ## Setup The Fizzy token is stored in the project `.env` file as `FIZZY_TOKEN`. Read it before making any API calls: ```bash grep '^FIZZY_TOKEN=' /Users/olly/dev/pagecord/.env | cut -d= -f2- ``` If `FIZZY_TOKEN` is missing or empty,
tools168
fizzy
Interact with the Fizzy tracker for Pagecord work. Use when the user asks to list, create, update, move, close, comment on, or inspect Fizzy cards or boards.
documentation168
pagecord
Interact with the Pagecord API for a blog. Use when the user wants to inspect posts or pages, publish content through the API, check API connectivity, or inspect the home page.
development168