{"id":16424,"plugin_id":"plugins_6a3d57a324b08191bc50d89df2647b45","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:13:23.456Z","digest":"6b769d71af0476818450b11b5c7f41c6c6fb6cc757e1a187b235f7163cc9e10e","against":null,"payload":{"name":"use-alpic","description":"Use Alpic Cloud and the `alpic` CLI for deployed MCP apps/servers, including deploys, builds, logs, debugging, environments, environment variables, tunnels, playgrounds, audits, auth, domains, IP restrictions, analytics, insights, versioning, and MCP Registry publishing.","included_files":[{"relative_path":"references/analytics.md","size_in_bytes":997},{"relative_path":"references/audit.md","size_in_bytes":896},{"relative_path":"references/auth.md","size_in_bytes":2784},{"relative_path":"references/builds.md","size_in_bytes":927},{"relative_path":"references/debug-deployment.md","size_in_bytes":935},{"relative_path":"references/deploy.md","size_in_bytes":784},{"relative_path":"references/domains.md","size_in_bytes":1371},{"relative_path":"references/endpoints.md","size_in_bytes":1232},{"relative_path":"references/environment-variable.md","size_in_bytes":1140},{"relative_path":"references/environments.md","size_in_bytes":1409},{"relative_path":"references/example-prompts.md","size_in_bytes":1218},{"relative_path":"references/git.md","size_in_bytes":1165},{"relative_path":"references/insights.md","size_in_bytes":1240},{"relative_path":"references/logs.md","size_in_bytes":865},{"relative_path":"references/network-security.md","size_in_bytes":1708},{"relative_path":"references/playground.md","size_in_bytes":1564},{"relative_path":"references/publish.md","size_in_bytes":853},{"relative_path":"references/tunnel.md","size_in_bytes":857},{"relative_path":"references/versioning.md","size_in_bytes":2061}],"skill_md_contents":"---\nname: use-alpic\ndescription: Use Alpic Cloud and the `alpic` CLI for deployed MCP apps/servers, including deploys, builds, logs, debugging, environments, environment variables, tunnels, playgrounds, audits, auth, domains, IP restrictions, analytics, insights, versioning, and MCP Registry publishing.\n---\n\n# Alpic Cloud\n\nAlpic hosts and operates MCP apps and servers. Use this skill for deployment,\nruntime operations, distribution, security, observability, and publishing on\nAlpic Cloud.\n\nThe reference files contain the task workflows and command details. Load only\nthe file(s) relevant to the user's request.\n\n## When To Use\n\n- The user mentions Alpic Cloud, `alpic`, Alpic deployments, Alpic logs, Alpic\n  playground, Alpic tunnels, Alpic environments, or Alpic publishing.\n- The user wants to operate an already-built MCP app/server.\n- The user wants production/distribution guidance after building an MCP app.\n\nUse `build-mcp-apps` instead when the work is primarily about designing or\nimplementing the MCP app/server itself.\n\n## References\n\nDeploy and operate:\n\n- Deploy an MCP app/server: [deploy.md](references/deploy.md)\n- Build configuration, runtimes, start commands: [builds.md](references/builds.md)\n- Failed deploys and startup failures: [debug-deployment.md](references/debug-deployment.md)\n- Runtime and deployment logs: [logs.md](references/logs.md)\n- Environment variables: [environment-variable.md](references/environment-variable.md)\n- Environments, branches, staging/preview/prod: [environments.md](references/environments.md)\n- GitHub auto-deploys: [git.md](references/git.md)\n- Local HTTPS tunnels: [tunnel.md](references/tunnel.md)\n\nInspect and test:\n\n- Usage metrics and project analytics: [analytics.md](references/analytics.md)\n- Readiness checks and launch audits: [audit.md](references/audit.md)\n- Playground configuration and headers: [playground.md](references/playground.md)\n- Playground example prompts: [example-prompts.md](references/example-prompts.md)\n- Public URLs and endpoint shapes: [endpoints.md](references/endpoints.md)\n\nSecure and distribute:\n\n- OAuth, DCR proxy, API-key protection: [auth.md](references/auth.md)\n- Fixed outbound IP and inbound IP whitelisting: [network-security.md](references/network-security.md)\n- Custom domains and DNS validation: [domains.md](references/domains.md)\n- User intents and feedback capture: [insights.md](references/insights.md)\n- Host caching and submitted-version strategy: [versioning.md](references/versioning.md)\n- MCP Registry publishing: [publish.md](references/publish.md)\n\n## Interface Choice\n\n- Prefer the `alpic` CLI for deploys, logs, environment variables,\n  environments, git, tunnels, audits, playground settings, and publishing.\n- Use the Alpic dashboard for custom domains, DCR client pools, fixed outbound\n  IP, inbound IP whitelisting, visual analytics, and Beacon rendering checks.\n- Use the hosted Alpic MCP server/app for agent-driven project browsing, logs,\n  and analytics when available.\n- Use REST APIs only for automation or gaps in CLI/MCP coverage.\n\n## Guardrails\n\n- Store secrets in Alpic environment variables, not source files.\n- Confirm the target project and environment before changing production config,\n  auth, domains, IP restrictions, fixed outbound IP, or environment variables.\n- Use build/deployment logs for deploy failures and runtime logs for live\n  behavior.\n- Re-deploy after changing environment variables.\n- Do not delete DCR client pools unless intentionally breaking existing client\n  registrations.\n- Publish only after a production deploy plus audit/playground verification.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}