CI/CD Pipeline Principles
irahardianto/awesome-agv
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
Install Frontmcp Production Readiness
$ npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentfront/frontmcp frontmcp-production-readiness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/libs/skills/catalog/frontmcp-production-readiness .claude/skills/frontmcp-production-readiness && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontmcp-production-readiness" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readiness into .claude/skills/frontmcp-production-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-production-readiness", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readinessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentfront/frontmcp frontmcp-production-readiness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/libs/skills/catalog/frontmcp-production-readiness .agents/skills/frontmcp-production-readiness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontmcp-production-readiness" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readiness into .agents/skills/frontmcp-production-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-production-readiness", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentfront/frontmcp frontmcp-production-readiness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/libs/skills/catalog/frontmcp-production-readiness .cursor/skills/frontmcp-production-readiness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontmcp-production-readiness" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readiness into .cursor/skills/frontmcp-production-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-production-readiness", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agentfront/frontmcp.git --path libs/skills/catalog/frontmcp-production-readiness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentfront/frontmcp frontmcp-production-readiness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/libs/skills/catalog/frontmcp-production-readiness .gemini/skills/frontmcp-production-readiness && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontmcp-production-readiness" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readiness into .gemini/skills/frontmcp-production-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-production-readiness", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agentfront/frontmcp frontmcp-production-readinessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/libs/skills/catalog/frontmcp-production-readiness .github/skills/frontmcp-production-readiness && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontmcp-production-readiness" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readiness into .github/skills/frontmcp-production-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-production-readiness", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentfront/frontmcp frontmcp-production-readiness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentfront/frontmcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/libs/skills/catalog/frontmcp-production-readiness .opencode/skills/frontmcp-production-readiness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontmcp-production-readiness" agent skill from https://github.com/agentfront/frontmcp/tree/main/libs/skills/catalog/frontmcp-production-readiness into .opencode/skills/frontmcp-production-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontmcp-production-readiness", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontmcp-production-readiness- GitHub stars
- 146
- Token cost
- ~6.5k tokens
- SKILL.md length
- 1,564 words
- Files
- 47 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
- Works in 3 steps: Detect Deployment Target → Run Common Checklist → Run Target-Specific Checklist
- Tasks that involve Security review
- SKILL.md covers When to Use This Skill, Prerequisites, Steps and Scenario Routing Table, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Frontmcp Production Readiness is an agent skill from agentfront/frontmcp. Pre-production audit, hardening, and go-live checklists for FrontMCP servers. Use before shipping to verify security hardening, performance, reliability, and observability, and for target-specific production checklists: Node server (Docker, graceful shutdown, Redis session scaling), Vercel and edge (cold-start, stateless design), AWS Lambda (cold start, scaling, monitoring), Cloudflare Workers (KV, Durable Objects, runtime limits), CLI binary and local daemon (stdio and socket transport), browser SDK bundle, and…
Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 53 other files, including reference files (for example `examples/common-checklist/caching-and-performance.md`, `examples/common-checklist/observability-setup.md` and `examples/common-checklist/security-hardening.md`).
It sits in DevOps & Cloud, covering Security review, Observability and Deployment. It works with Vercel, Cloudflare Workers, Docker and npm. The repository describes itself as: TypeScript-first framework for the Model Context Protocol (MCP). You write clean, typed code; FrontMCP handles the protocol, transport, DI, session/auth, and execution flow. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Security review
- Tasks that involve Observability
- Tasks that involve Deployment
Example prompts
- “/frontmcp-production-readiness”
Requirements
- Node.js
- Docker
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e7c4d71. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.agentfront.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Frontmcp Production Readiness loads about 6.5k tokens when it runs, and up to ~23k if it reads all its reference files. Until then it costs about 218 tokens; SKILL.md has 1,564 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from agentfront/frontmcp at commit e7c4d71, republished under its Apache-2.0 licence (© agentfront). 1,564 words, ~6,517 tokens.
Download SKILL.mdSave it as
.claude/skills/frontmcp-production-readiness/SKILL.md (or your agent's skills folder). This skill also uses 46 other files; get the full folder from GitHub.- name
- frontmcp-production-readiness
- description
- Pre-production audit, hardening, and go-live checklists for FrontMCP servers. Use before shipping to verify security hardening, performance, reliability, and observability, and for target-specific production checklists: Node server (Docker, graceful shutdown, Redis session scaling), Vercel and edge (cold-start, stateless design), AWS Lambda (cold start, scaling, monitoring), Cloudflare Workers (KV, Durable Objects, runtime limits), CLI binary and local daemon (stdio and socket transport), browser SDK bundle, and embedded npm SDK. Also configuring /healthz and /readyz health and readiness endpoints with custom probes, and distributed high-availability (multi-pod heartbeat, session takeover, notification relay). Triggers: production ready, security audit, hardening, performance check, production checklist, go live, pre-launch review.
- tags
- production, security, performance, reliability, observability, audit, best-practices
- category
- production
- targets
- all
- bundle
- recommended, full
- priority
- 10
- visibility
- both
- license
- Apache-2.0
- metadata.docs
- https://docs.agentfront.dev/frontmcp/deployment/production-build
FrontMCP Production Readiness Audit
Router for production readiness checklists. Start with the common checklist (security, performance, reliability, observability), then follow the target-specific checklist for your deployment environment.
When to Use This Skill
Must Use
- Before deploying a FrontMCP server to production for the first time
- After major feature additions or architectural changes
- During security reviews or compliance audits
Recommended
- As part of PR reviews for infrastructure-touching changes
- Quarterly health checks on production deployments
- When switching deployment targets
Skip When
- Building a prototype or proof-of-concept
- Running in development/local mode only
Decision: Use this skill when preparing for production. Start with
common-checklist, then pick your deployment target.
Prerequisites
- A deployable FrontMCP project (build target chosen, see
frontmcp-deployment). - Observability and structured logging available (see
frontmcp-observability) — production hardening assumes you can see what the server is doing. - A staging environment matching production target (Node, Vercel, Lambda, Cloudflare, CLI, browser) to validate the checklist before go-live.
Steps
Step 1: Detect Deployment Target
Check the project to determine the deployment target:
- Look at
package.jsonscripts forfrontmcp build --target <target> - Check for target-specific files:
ci/Dockerfile(node),vercel.json(vercel),wrangler.toml(cloudflare),ci/template.yaml(lambda) - Check if the build target is
cliorbrowserin the build config - If unclear, ask the user which environment they're deploying to
Step 2: Run Common Checklist
Always start with the common checklist — it covers security, performance, reliability, and observability that apply to every target.
Step 3: Run Target-Specific Checklist
After the common checklist, run the checklist for your deployment target.
Scenario Routing Table
| Scenario | Reference | Description |
|---|---|---|
| Common security, performance, reliability, observability | references/common-checklist.md | Applies to ALL targets — run this first |
| Health & readiness endpoints (/healthz, /readyz) | references/health-readiness-endpoints.md | Custom probes, Kubernetes, runtime-aware readiness |
| Standalone Node.js server with Docker | references/production-node-server.md | Docker, health checks, Redis, scaling, CI/CD |
| Node.js SDK / direct client (npm package) | references/production-node-sdk.md | create()/connect() API, disposal, npm publishing |
| Vercel serverless / edge | references/production-vercel.md | Vercel config, edge runtime, cold starts, Vercel KV |
| Cloudflare Workers | references/production-cloudflare.md | Wrangler, Workers runtime, KV, Durable Objects |
| AWS Lambda | references/production-lambda.md | SAM template, cold starts, DynamoDB, API Gateway |
| CLI daemon (local MCP server) | references/production-cli-daemon.md | Process manager, socket files, service registration |
| CLI binary (one-shot execution) | references/production-cli-binary.md | Fast startup, stdio transport, exit codes, npm bin |
| Browser SDK | references/production-browser.md | Bundle size, browser APIs, CSP, CDN distribution |
Quick Reference: Target Detection
| File / Signal Found | Target |
|---|---|
ci/Dockerfile or ci/docker-compose.yml | Standalone server → production-node-server.md |
serve: false or create() API usage | SDK / direct client → production-node-sdk.md |
vercel.json | Vercel → production-vercel.md |
wrangler.toml | Cloudflare → production-cloudflare.md |
ci/template.yaml | Lambda → production-lambda.md |
frontmcp start / socket / service install usage | CLI daemon → production-cli-daemon.md |
build --target cli + bin in package.json | CLI binary → production-cli-binary.md |
build --target browser in scripts | Browser → production-browser.md |
Common Patterns
| Pattern | Correct | Incorrect | Why |
|---|---|---|---|
| Checklist order | Common checklist first, target-specific second | Skip straight to vendor checklist | Common items (auth, rate limits, observability) gate all targets |
| Storage | Redis / Vercel KV in production | In-memory session/elicitation stores | Memory stores reset on every cold start and don't span replicas |
| Health checks | /healthz (liveness) + /readyz (readiness) endpoints | Single /health endpoint that always returns 200 | Kubernetes/load balancers need separate liveness vs readiness signals |
| Secret loading | Read from env vars (process.env.X) | Hardcode tokens / paste into config | Hardcoded secrets leak via the build artefact and source control |
| Build verification | Run frontmcp doctor + smoke test against built artefact | Trust local dev mode behaviour | Production targets (Vercel, Lambda, Cloudflare, browser) have different runtimes |
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Sessions disappear after a deploy | Memory session store on a stateless platform | Switch to Redis / Vercel KV; see setup-redis and configure-session |
| Liveness probe passes while requests fail | /healthz doesn't exercise the request path | Add /readyz that checks dependencies (DB, Redis, downstream APIs); see health-readiness-endpoints |
| Cold-start latency above SLA | Heavy provider construction at request time | Construct shared clients in module scope or onInit; see production-vercel / production-lambda |
| Rate-limit exceeded under normal load | Global throttle too tight, no per-tool overrides | Tune throttle.requestsPerSecond; add per-tool overrides; see configure-throttle |
frontmcp doctor flags missing observability | Observability disabled or not wired | Set observability: true in @FrontMcp and configure a sink; see frontmcp-observability |
| Browser build exceeds bundle budget | Server-only deps imported into the browser entry | Split entries; gate Node-only imports behind availableWhen.platform; see production-browser |
Verification Checklist
After completing both common and target-specific checklists:
- Run
frontmcp doctorto check project configuration - Run
frontmcp testto ensure all tests pass - Run
frontmcp buildto verify production build succeeds - Deploy to staging and run E2E tests against it
- Review logs for any warnings or errors during startup
- Update README for the deployment target (see
frontmcp-setup→references/readme-guide.md)
Examples
Each reference has matching examples under examples/<reference>/:
common-checklist
| Example | Level | Description |
|---|---|---|
caching-and-performance | Advanced | Shows how to configure caching with TTL, optimize responses, and manage memory with proper provider lifecycle cleanup. |
observability-setup | Intermediate | Shows how to configure structured logging, error handling with MCP error codes, and monitoring integration for production. |
security-hardening | Basic | Shows how to configure authentication, CORS, input validation, and rate limiting for a production FrontMCP server. |
production-browser
| Example | Level | Description |
|---|---|---|
browser-bundle-config | Basic | Shows how to configure package.json for browser-compatible SDK distribution with ESM/CJS/UMD entry points, TypeScript declarations, and CDN support. |
cross-platform-crypto | Intermediate | Shows how to use @frontmcp/utils for cross-platform crypto operations that work in both browser and Node.js, and how to avoid Node.js-only APIs. |
security-and-performance | Advanced | Shows how to ensure no secrets are bundled in browser code, configure CSP headers on the server, optimize bundle size, and avoid blocking the main thread. |
production-cli-binary
| Example | Level | Description |
|---|---|---|
binary-build-config | Basic | Shows how to configure a FrontMCP CLI binary with correct package.json bin field, shebang, stdio transport, and npm distribution settings. |
stdio-transport-error-handling | Intermediate | Shows how to handle stdin/stdout transport correctly, implement proper exit codes, and handle edge cases like EOF and broken pipes. |
Show full SKILL.md (632 more words)Show less
production-cli-daemon
| Example | Level | Description |
|---|---|---|
daemon-socket-config | Basic | Shows how to configure a FrontMCP server as a long-running local daemon with Unix socket transport, process management, and SQLite storage. |
graceful-shutdown-cleanup | Intermediate | Shows how to implement graceful shutdown for a daemon process, including completing in-flight requests, closing database connections, removing the socket file, and cleaning up the PID file. |
security-and-permissions | Advanced | Shows how to secure a local daemon with restrictive socket permissions, XDG-compliant config storage, and file-based secret management. |
production-cloudflare
| Example | Level | Description |
|---|---|---|
durable-objects-state | Advanced | Shows how to use Cloudflare Durable Objects for stateful coordination alongside the stateless Workers runtime, with KV for cache and R2 for blob storage. |
workers-runtime-constraints | Intermediate | Shows how to write tools that are compatible with the Cloudflare Workers runtime: no Node.js APIs, no eval, only async I/O, and using Web APIs. |
wrangler-config | Basic | Shows how to configure wrangler.toml with correct routes, KV bindings for session storage, and secret management for a FrontMCP Cloudflare Worker. |
production-lambda
| Example | Level | Description |
|---|---|---|
cold-start-connection-reuse | Intermediate | Shows how to minimize Lambda cold starts with lazy initialization, tree-shaking, and the connection reuse pattern for external services. |
sam-template | Basic | Shows a complete SAM/CloudFormation template for deploying a FrontMCP server to AWS Lambda with API Gateway routing, DynamoDB for session storage, and proper environment configuration. |
scaling-and-monitoring | Advanced | Shows how to configure concurrency limits, dead letter queues, provisioned concurrency, and CloudWatch alarms for a production Lambda deployment. |
production-node-sdk
| Example | Level | Description |
|---|---|---|
basic-sdk-lifecycle | Basic | Shows the complete lifecycle of a FrontMCP SDK package used as an embedded client: initialization, tool invocation, and proper cleanup. |
multi-instance-cleanup | Advanced | Shows how multiple SDK instances can coexist without conflicts, and how to implement proper cleanup to prevent memory leaks from event listeners, timers, and provider resources. |
package-json-config | Intermediate | Shows the correct package.json configuration for publishing a FrontMCP SDK package with CJS + ESM entry points, peer dependencies, and proper file inclusions. |
production-node-server
| Example | Level | Description |
|---|---|---|
docker-multi-stage | Basic | Shows a production-ready Dockerfile with multi-stage build, non-root user, and container health check for a FrontMCP Node.js server. |
graceful-shutdown | Intermediate | Shows how to implement graceful shutdown with SIGTERM handling, in-flight request draining, and health check status transitions. |
redis-session-scaling | Advanced | Shows how to configure Redis-backed session storage, connection pooling, and stateless server design for horizontal scaling behind a load balancer. |
production-vercel
| Example | Level | Description |
|---|---|---|
cold-start-optimization | Intermediate | Shows how to minimize cold start time by lazy-loading dependencies, avoiding heavy initialization at module scope, and caching expensive operations. |
stateless-serverless-design | Advanced | Shows a fully stateless server design that works on Vercel edge runtime with no Node.js-only APIs, using @frontmcp/utils for cross-platform crypto. |
vercel-edge-config | Basic | Shows how to configure a FrontMCP server for Vercel deployment with Vercel KV for session storage and correct route configuration. |
health-readiness-endpoints
| Example | Level | Description |
|---|---|---|
basic-health-setup | Basic | Default health endpoints with Redis session store, showing /healthz and /readyz responses. |
custom-probes | Intermediate | Custom database and API probes with Kubernetes deployment configuration. |
distributed-ha
| Example | Level | Description |
|---|---|---|
ha-kubernetes-3-replicas | Intermediate | Deploy FrontMCP with 3 replicas, Redis, and automatic session failover on Kubernetes |
Accessing This Skill
Skills are distributed as plain SKILL.md files plus a sibling references/
and examples/ tree, so consumers can pick whichever access mode fits:
| Mode | How it works |
|---|---|
| Filesystem | Read libs/skills/catalog/frontmcp-production-readiness/ directly from a clone of the catalog repo, or from a published @frontmcp/skills install. SKILL.md is the entry point. |
frontmcp CLI | frontmcp skills list, frontmcp skills read frontmcp-production-readiness, frontmcp skills read frontmcp-production-readiness:references/<file>.md, frontmcp skills install frontmcp-production-readiness — no server required. |
MCP skill:// | When a developer mounts this skill into their own FrontMCP server (@FrontMcp({ skills: [...] })), the SDK exposes it via SEP-2640 resources: skill://frontmcp-production-readiness/SKILL.md, skill://frontmcp-production-readiness/references/{file}.md, etc. The server’s skill://index.json returns the SEP-2640 discovery document for everything mounted on it. |
The catalog itself is not an MCP server. The skill:// URIs only resolve
when a server has been configured to host this skill.
Reference
- Production Build
- Related skills:
frontmcp-config,frontmcp-deployment,frontmcp-testing,frontmcp-setup,frontmcp-observability
© agentfront, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 46 other files (references) in libs/skills/catalog/frontmcp-production-readiness of agentfront/frontmcp.
- SKILL.md
- examples/common-checklist/caching-and-performance.md
- examples/common-checklist/observability-setup.md
- examples/common-checklist/security-hardening.md
- examples/distributed-ha/ha-kubernetes-3-replicas.md
- examples/health-readiness-endpoints/basic-health-setup.md
- examples/health-readiness-endpoints/custom-probes.md
- examples/production-browser/browser-bundle-config.md
- examples/production-browser/cross-platform-crypto.md
- examples/production-browser/security-and-performance.md
- examples/production-cli-binary/binary-build-config.md
- examples/production-cli-binary/stdio-transport-error-handling.md
- examples/production-cli-daemon/daemon-socket-config.md
- examples/production-cli-daemon/graceful-shutdown-cleanup.md
- … and 33 more
Open the folder on GitHubat commit e7c4d71
Compare with similar skills
Frontmcp Production Readiness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frontmcp Production Readiness this skillagentfront/frontmcp | 146 | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| CI/CD Pipeline Principlesirahardianto/awesome-agv | 156 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Reflexo ReleaseMyriad-Dreamin/typst.ts | 1.2k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Onboarding Validationopen-edge-platform/edge-ai-suites | 140 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Devops InfrastructureCloudAI-X/claude-workflow-v2 | 1.4k | — | ~2.7k | Automated safety check: Notes | MIT | |
| Devops SpecialistCaoMeiYouRen/caomei-auth | 220 | — | ~446 | Automated safety check: Notes | MIT |
Similar skills
Reflexo Release
Myriad-Dreamin/typst.ts
Guide Reflexo/typst.ts release preparation and operator handoffs.
Onboarding Validation
open-edge-platform/edge-ai-suites
Validate the get-started experience of Open Edge Platform (OEP) software components from the perspective of a first-time user.
Devops Infrastructure
CloudAI-X/claude-workflow-v2
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup.
Devops Specialist
CaoMeiYouRen/caomei-auth
修改 Docker、CI/CD、部署配置、环境变量、运行时参数、构建脚本和发布流程时使用。优先覆盖 Docker、Vercel、Cloudflare 与 GitHub Actions 场景。用户提到 deploy、Dockerfile、workflow、CI、CD、environment variables、build pipeline、release config 时都应触发。
Supercheck Infrastructure Deployment
supercheck-io/supercheck
Work on Supercheck Docker Compose, K3s, Kubernetes manifests, gVisor, OpenTofu/Hetzner, secrets, external services, autoscaling, backups, disaster recovery, DNS/TLS, or production deployment.
More from agentfront/frontmcp
All 12 skills in this repoFrontmcp Auth UI
agentfront/frontmcp
A skill your agent uses when customizing, branding, or replacing the built-in FrontMCP OAuth pages (the login, consent, federated-select, incremental-authorization, and error pages) with your own…
Frontmcp Channels
agentfront/frontmcp
A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.
Frontmcp Extensibility
agentfront/frontmcp
A skill your agent uses when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools.
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Frontmcp Authorities
agentfront/frontmcp
A skill your agent uses when implementing authorization and access control for FrontMCP tools, resources, prompts, or skills, deciding who may invoke what.
Frontmcp Config
agentfront/frontmcp
A skill your agent uses when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options.
Related
Categories
Questions about Frontmcp Production Readiness
What does Frontmcp Production Readiness do?
Pre-production audit, hardening, and go-live checklists for FrontMCP servers. Frontmcp Production Readiness is an agent skill from agentfront/frontmcp. Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
When should I use Frontmcp Production Readiness?
Frontmcp Production Readiness fits situations like: tasks that involve Security review; tasks that involve Observability; tasks that involve Deployment.
How do I install Frontmcp Production Readiness in Claude Code?
Run `npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a claude-code`. Or copy the skill folder (libs/skills/catalog/frontmcp-production-readiness in agentfront/frontmcp) into .claude/skills/frontmcp-production-readiness in your project. Claude Code loads it when a task matches its description.
How do I install Frontmcp Production Readiness in Codex?
Run `npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a codex`. Or copy the skill folder (libs/skills/catalog/frontmcp-production-readiness in agentfront/frontmcp) into .agents/skills/frontmcp-production-readiness in your project. Codex loads it when a task matches its description.
Can I use Frontmcp Production Readiness in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentfront/frontmcp --skill frontmcp-production-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontmcp-production-readiness, .gemini/skills/frontmcp-production-readiness, .github/skills/frontmcp-production-readiness and .opencode/skills/frontmcp-production-readiness in your project.
What does Frontmcp Production Readiness need to run?
SKILL.md names no scripts, command-line tools or credentials: Frontmcp Production Readiness is instructions for the agent only. Our summary lists: Node.js; Docker.
Does Frontmcp Production Readiness access the network?
SKILL.md names 1 domain. As links in the text: docs.agentfront.dev. This is read from the text; nothing was executed.
Is Frontmcp Production Readiness safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Frontmcp Production Readiness use?
Frontmcp Production Readiness is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frontmcp Production Readiness use?
About 6.5k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.
What are the alternatives to Frontmcp Production Readiness?
Skills that share tags, products or a category with Frontmcp Production Readiness: CI/CD Pipeline Principles (irahardianto/awesome-agv, 156 stars), Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars), Onboarding Validation (open-edge-platform/edge-ai-suites, 140 stars) and Devops Infrastructure (CloudAI-X/claude-workflow-v2, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frontmcp Production Readiness?
agentfront (a GitHub organization) maintains it in agentfront/frontmcp, which has 146 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 10, 2026.
Source: agentfront/frontmcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.