golang-echo-zap
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: golang-echo-zap
description: Use when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. U…
category: engineering
runtime: no special runtime
---
# golang-echo-zap output preview
## PART A: Task fit
- Use case: Use when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. Use this skill when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Use When / Key Facts / Minimal Setup” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. Use this skill when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Use When / Key Facts / Minimal Setup” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Use When / Key Facts / Minimal Setup”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: golang-echo-zap
description: Use when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. U…
category: engineering
source: tomevault-io/skills-registry
---
# golang-echo-zap
## When to use
- Use when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service. Use this skill when add…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Use When / Key Facts / Minimal Setup” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "golang-echo-zap" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Use When / Key Facts / Minimal Setup
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} golang-echo-zap
Use this skill when adding or configuring github.com/adlandh/echo-zap-middleware/v2 in a Go Echo service.
Use When
- The user wants Zap request logging in an Echo app.
- Code imports
github.com/adlandh/echo-zap-middleware/v2or needs this middleware configured. - The task mentions
ZapConfig,Middleware,MiddlewareWithContextLogger,BodySkipper, request/response body logging, or Echo request IDs.
Key Facts
- This middleware targets
github.com/labstack/echo/v5; do not mix it with Echo v4 imports. - Echo v5 handlers and skippers use
*echo.Context, notecho.Context. - Import path is
github.com/adlandh/echo-zap-middleware/v2; package name isechozapmiddlewareunless aliased. Middleware(logger, config...)is the normal entrypoint for a*zap.Logger.MiddlewareWithContextLogger(ctxLogger, config...)is forgithub.com/adlandh/context-loggerextractors.ZapConfigfills defaults only for nilSkipperand nilBodySkipper; bool and int zero values are meaningful.LimitHTTPBody: truewithLimitSize <= 0disables body limiting.BodySkipperdoes not prevent body capture; it replaces non-empty logged bodies with[excluded].- Request IDs are logged from request
X-Request-Idfirst, then from Echo's response header.
Minimal Setup
import (
echozapmiddleware "github.com/adlandh/echo-zap-middleware/v2"
"github.com/labstack/echo/v5"
"github.com/labstack/echo/v5/middleware"
"go.uber.org/zap"
)
logger, err := zap.NewProduction()
if err != nil {
return err
}
e := echo.New()
e.Use(middleware.RequestID())
e.Use(echozapmiddleware.Middleware(logger))
Body And Header Logging
e.Use(echozapmiddleware.Middleware(logger, echozapmiddleware.ZapConfig{
AreHeadersDump: true,
IsBodyDump: true,
LimitHTTPBody: true,
LimitSize: 500,
Skipper: func(c *echo.Context) bool {
return c.Path() == "/health"
},
BodySkipper: func(c *echo.Context) (skipReqBody, skipRespBody bool) {
if c.Path() == "/upload" {
return true, false
}
if c.Request().Header.Get("Content-Encoding") == "gzip" {
return true, true
}
return false, false
},
}))
Context Logger Setup
import contextlogger "github.com/adlandh/context-logger"
ctxLogger := contextlogger.WithContext(logger)
e.Use(echozapmiddleware.MiddlewareWithContextLogger(ctxLogger))
Implementation Guidance
- Add
middleware.RequestID()before this middleware when generated request IDs should appear in logs. - Keep body dumping off by default for hot paths; enable
IsBodyDumponly when the service can afford body capture. - Use
BodySkipperfor sensitive or binary payloads, but still setLimitHTTPBodyandLimitSizefor large bodies. - If changing middleware behavior in this repo, preserve downstream request body replay after capture and update README configuration docs.
Verify
- In this repo, run
go test ./...for a fast check. - For body limit changes, run
go test -run TestLimitBody ./...andgo test -run 'TestMiddleware/TestBodyLimitApplied' ./.... - CI uses
go test -race -coverprofile=coverage.txt -covermode=atomic ./....
Source: adlandh/echo-zap-middleware — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review