Skip to main content
Execute qualquer Skill no Manus
com um clique
Repositório GitHub

pixoo-mcp-server

pixoo-mcp-server contém 6 skills coletadas de cyanheads, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.

skills coletadas
6
Stars
5
atualizado
2026-06-12
Forks
0
Cobertura ocupacional
2 categorias ocupacionais · 100% classificado
explorador de repositórios

Skills neste repositório

api-auth
Desenvolvedores de software

Authentication, 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.

2026-06-12
api-errors
Desenvolvedores de software

McpError 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.

2026-06-12
api-services
Desenvolvedores de software

API reference for built-in service providers (LLM, Speech, Graph). Use when looking up service interfaces, provider capabilities, or integration patterns.

2026-06-12
api-telemetry
Desenvolvedores de software

Catalog 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.

2026-06-12
report-issue-local
Desenvolvedores de software

File 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.

2026-06-12
tool-defs-analysis
Analistas de garantia de qualidade de software e testadores

Read-only audit of MCP definition language across an existing surface — tools, resources, prompts. Walks every definition file and checks 12 categories the LLM reads to decide whether and how to call: voice & tense, internal leaks, audience leaks, defaults, recovery hints, output descriptions, cross-references, sparsity, examples, structure, mutator observability, unit-bearing numeric names. Produces grouped findings with file:line citations and a numbered options list. Use during polish, after a refactor, or before a release. Complements `field-test` (behavior testing) and `security-pass` (security audit).

2026-06-12