All authors
Claude Skills by jiayaoqijia
github.com/jiayaoqijia2,216 skills3 installs4,789 views
- Cyanheads Add TestScaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.Votes: 0GitHub stars: 76
- Cyanheads Add ToolScaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.Votes: 0GitHub stars: 76
- Cyanheads Api AuthAuthentication, authorization, and multi-tenancy patterns for `@cyanheads/mcp-ts-core`. Use when implementing auth scopes on tools/resources, configuring auth modes (none/jwt/oauth), working with JWT/OAuth env vars, or understanding how tenantId flows through ctx.state.Votes: 0GitHub stars: 76
- Cyanheads Api CanvasDataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for multi-agent collaboration, env config, and Cloudflare Workers fail-closed behavior.Votes: 0GitHub stars: 76
- Cyanheads Api ConfigReference for core and server configuration in `@cyanheads/mcp-ts-core`. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.Votes: 0GitHub stars: 76
- Cyanheads Api ContextCanonical reference for the unified `Context` object passed to every tool and resource handler in `@cyanheads/mcp-ts-core`. Covers the full interface, its `RequestContext` base, all sub-APIs (`ctx.log`, `ctx.state`, `ctx.requestInput`, `ctx.inputs`, `ctx.enrich`, `ctx.content`), and when to use each.Votes: 0GitHub stars: 76
- Cyanheads Api ErrorsMcpError constructor, JsonRpcErrorCode reference, and error handling patterns for `@cyanheads/mcp-ts-core`. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.Votes: 0GitHub stars: 76
- Cyanheads Api LinterMCP definition linter rules reference. Use when `bun run lint:mcp` or `bun run devcheck` reports a lint error or warning (`format-parity`, `schema-is-object`, `name-format`, `server-json-*`, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.Votes: 0GitHub stars: 76
- Cyanheads Api MirrorStand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.Votes: 0GitHub stars: 76
- Cyanheads Api ServicesAPI reference for built-in service providers (LLM, Speech, Graph). Use when looking up service interfaces, provider capabilities, or integration patterns.Votes: 0GitHub stars: 76
- Cyanheads Api TelemetryCatalog of OpenTelemetry instrumentation built into framework `@cyanheads/mcp-ts-core` — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up attribute names, or deciding what's safe to put on a metric attribute vs. a span.Votes: 0GitHub stars: 76
- Cyanheads Api TestingTesting patterns for MCP tool/resource handlers using `createMockContext` and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.Votes: 0GitHub stars: 76
- Cyanheads Api UtilsAPI reference for all utilities exported from `@cyanheads/mcp-ts-core/utils`. Use when looking up utility method signatures, options, peer dependencies, or usage patterns.Votes: 0GitHub stars: 76
- Cyanheads Api WorkersCloudflare Workers deployment using `createWorkerHandler` from `@cyanheads/mcp-ts-core/worker`. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.Votes: 0GitHub stars: 76
- Cyanheads Code SimplifierCode review and cleanup against a working tree of changes, or against a named path or whole codebase. Analyzes `git diff` (or the named target) to simplify, consolidate, and align code with the existing codebase — modernize syntax, remove unnecessary complexity, consolidate duplicated logic, catch efficiency issues. Use after a substantive working session, or when asked to clean up, simplify, reduce slop, consolidate, modernize, tighten up, de-slop, or scan a codebase. For `@cyanheads/mcp-ts-...Votes: 0GitHub stars: 76
- Cyanheads Design Mcp ServerDesign the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.Votes: 0GitHub stars: 76
- Cyanheads Field TestExercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to test, try out, or verify their MCP surface.Votes: 0GitHub stars: 76
- Cyanheads Git WrapupLand working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to main, no publish: the release-and-publish skill merges, tags, and ships from here. Distilled from th...Votes: 0GitHub stars: 76
- Cyanheads MaintenanceInvestigate, adopt, and verify dependency updates — with special handling for `@cyanheads/mcp-ts-core`. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or review updates you already applied.Votes: 0GitHub stars: 76
- Cyanheads OrchestrationsPick and run a multi-phase workflow that chains foundational task skills (`git-wrapup`, `release-and-publish`, `maintenance`, `field-test`, `setup`, etc.) end-to-end. Routes user intent to a workflow file under `workflows/` — greenfield builds, maintenance + release, field-test + fix, or known-work + release. Single source for the universal rules (no commits without authorization, no destructive git, no marketing language), the orchestrator posture (own the goal, ground sub-agents in primary ...Votes: 0GitHub stars: 76
- Cyanheads Polish Docs MetaFinalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.Votes: 0GitHub stars: 76
- Cyanheads Release And PublishShip a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for `.mcpb` bundles, GHCR). Runs the final verification gate, fast-forwards `main` when the release rode a release PR, creates the annotated tag on the commit `main` now points at, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit stack — and in release PR mode, the pushed branch and open PR) is already complete — th...Votes: 0GitHub stars: 76
- Cyanheads Release Pr ReviewReview pass on an open release PR (`release/<version>` → `main`) — the step between `git-wrapup` and `release-and-publish` when a project releases in gated release PR mode. Reads the PR's commit range through the `code-simplifier` lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as ordinary commits on top of the release branch and pushes it, keeps the PR body in sync with what ships, and leaves one summary comment. The only agent role that bo...Votes: 0GitHub stars: 76
- Cyanheads Report Issue FrameworkFile a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.Votes: 0GitHub stars: 76
- Cyanheads Report Issue LocalFile a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.Votes: 0GitHub stars: 76
- Cyanheads Security PassReview an MCP server for common security gaps: LLM-facing surfaces as injection vector (tools, resources, prompts, descriptions), scope blast radius, destructive ops without consent, upstream auth shape, input sinks (URL / path / roots / shell / schema strictness / ReDoS), tenant isolation, leakage through errors and telemetry, unbounded resources, and HTTP-mode deployment surface. Use before a release, after a batch of handler changes, or when the user asks for a security review, audit, or h...Votes: 0GitHub stars: 76
- Cyanheads SetupPost-init orientation for an MCP server built on @cyanheads/mcp-ts-core. Use after running `@cyanheads/mcp-ts-core init` to understand the project structure, conventions, and skill sync model. Also use when onboarding to an existing project for the first time.Votes: 0GitHub stars: 76
- Cyanheads TechniquesCatalog of reusable response- and data-shaping techniques for MCP servers built on `@cyanheads/mcp-ts-core` — overflow handling, payload shaping, retrieval patterns. Use when a tool's payload is too large, awkwardly shaped, or expensive to retrieve and you want a proven pattern instead of inventing one. Each technique has a self-contained reference under `references/`.Votes: 0GitHub stars: 76
- Cyanheads Tool Defs AnalysisRead-only audit of MCP definition language across an existing surface — tools, resources, prompts, server instructions. Walks every definition file and checks 16 categories the LLM reads to decide whether and how to call: voice & tense, internal leaks, audience leaks, defaults, recovery hints, field descriptions, cross-references, sparsity, examples, structure, mutator observability, unit-bearing numeric names, validator-enforced constraints, annotations truthfulness, single-line strings, exc...Votes: 0GitHub stars: 76
- Danthamanvoiss Affiliate EnablementDraft partner onboarding, positioning, referral process, and compliance guardrails.Votes: 0GitHub stars: 76
- Danthamanvoiss Agency RouterTop-level agency-skills-router that resolves context first, then routes to the smallest reliable skill set.Votes: 0GitHub stars: 76
- Danthamanvoiss Ai Citability Content ReviewImprove direct-answer, evidence-rich, self-contained content without fake citations.Votes: 0GitHub stars: 76
- Danthamanvoiss Ai Content Pipeline BuilderDesign reusable prompt-chaining workflows for cohesive multi-step AI content production.Votes: 0GitHub stars: 76
- Danthamanvoiss Ai Creative RouterRoute AI-creative quality, pipeline, prompt-translation, and cross-asset consistency work to the right support skill.Votes: 0GitHub stars: 76
- Danthamanvoiss Anti Slop Content ReviewReview AI-generated creative outputs for generic/sloppy patterns and rewrite guidance for stronger taste.Votes: 0GitHub stars: 76
- Danthamanvoiss Appointment Setting PlaybookDraft appointment-setting sequences, qualification gates, and calendar handoff prompts using supplied lead context.Votes: 0GitHub stars: 76
- Danthamanvoiss Brand Client Context OnboardingDetect existing harness or file-based brand/client context, then fill only the missing gaps with reusable onboarding drafts.Votes: 0GitHub stars: 76
- Danthamanvoiss Brand Context Brief BuilderBuild or refresh reusable brand and client context briefs using known platform defaults first, then explicit gaps.Votes: 0GitHub stars: 76
- Danthamanvoiss Brand Visual Identity BriefDraft visual identity brief covering style direction, usage constraints, and deliverable requirements.Votes: 0GitHub stars: 76
- Danthamanvoiss Campaign PlanBuild objective/audience/channel/asset/measurement plan with budget assumptions.Votes: 0GitHub stars: 76
- Danthamanvoiss Catalog Maintenance GuideKeep catalog entries, paths, versions, categories, and counts aligned when the static skill library changes.Votes: 0GitHub stars: 76
- Danthamanvoiss Churn Risk Early WarningAssess churn risk signals from supplied account data and produce early-warning mitigation drafts.Votes: 0GitHub stars: 76
- Danthamanvoiss Client Onboarding PlanBuild kickoff plan, access checklist, timeline, communication rhythm, and success measures.Votes: 0GitHub stars: 76
- Danthamanvoiss Client Success RouterRoute onboarding, review, retention, and expansion work to the right client-success skill with concise lifecycle clarification.Votes: 0GitHub stars: 76
- Danthamanvoiss Content CalendarGenerate a 30-day content plan from provided business context and goals.Votes: 0GitHub stars: 76
- Danthamanvoiss Context First Workflow GuideDocument the simplest reliable order for resolving context, routing work, and handing outputs between skills.Votes: 0GitHub stars: 76
- Danthamanvoiss Context LoaderResolve the best available harness, agency, or client context before running downstream skills.Votes: 0GitHub stars: 76
- Danthamanvoiss Creative Brief GeneratorGenerate cross-functional creative requirements briefs for downstream execution teams and tools.Votes: 0GitHub stars: 76
- Danthamanvoiss Crm Workflow BlueprintDraft CRM workflow blueprint documentation covering lifecycle stages, owners, fields, and governance.Votes: 0GitHub stars: 76
- Danthamanvoiss Cross Asset Consistency CheckCheck consistency of messaging, style, and factual claims across multiple creative assets.Votes: 0GitHub stars: 76