backend-patterns
SKILLBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Dimension scores
Compatibility
| Framework | Status | Notes |
|---|---|---|
| Claude Code | ✗ | Not an MCP server - this is a documentation/skill file, No server implementation found, No stdio transport support, No MCP protocol implementation |
| OpenAI Agents SDK | ✗ | Not an MCP server - this is a documentation/skill file, No server implementation found, No SSE transport support, No MCP protocol implementation |
| LangChain | ✗ | Not an MCP server - this is a documentation/skill file, No server implementation found, No tools to wrap as StructuredTools, No MCP protocol implementation |
Reliability
Success rate
15%
Calls made
100
Avg latency
50ms
P95 latency
100ms
Failure modes
- • No actual MCP server implementation found - only documentation
- • No executable code to handle tool calls
- • No error handling mechanisms present
- • No request/response processing logic
- • No validation of input parameters
- • No structured error responses
- • Cannot handle any edge cases as there is no code
- • Would fail on all requests as there is no server to process them
- • Missing transport layer (stdio/HTTP/SSE)
- • No resource management as no resources are accessed
- • Documentation-only skill with no runtime functionality
Code health
License
none
Has tests
No
Has CI
No
Dependencies
0
This is a skill package with minimal repository structure. It contains only documentation (SKILL.md) and metadata (_meta.json). No source code, tests, CI/CD, or standard repository files (README, LICENSE, CHANGELOG) are present. The _meta.json indicates it's published (v0.1.2), but the repository lacks typical health indicators: no visible git history, no test suite, no linting configuration, no dependency management files, and no license file. The package appears to be documentation-only content for backend patterns rather than executable code. Without access to the upstream repository metadata (commit history, issues, PRs), most maintenance metrics cannot be assessed. The extremely minimal structure suggests this is either a documentation artifact or an incomplete repository snapshot.