클라우드, CI/CD, 모니터링, 배포 (7.3천건)
Sub-skill: Implement Auth.md for agent registration discovery. Serve /auth.md with OAuth metadata at /.well-known/oauth-protected-resource and authorization server endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sub-skill de agent-ready-cloudflare: Implement AI Bot Rules in robots.txt
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sub-skill de agent-ready-cloudflare: Implement API Catalog
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sub-skill de agent-ready-cloudflare: Implement Agent Skills Discovery Index
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sub-skill de agent-ready-cloudflare: Implement A2A Agent Card
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user needs to consume the Pier Cloud (Lighthouse) API for cloud cost management — including JWT authentication, listing contexts, workspaces, workspace groups, and FinOps data views. Trigger whenever there is a need to integrate, automate, or debug calls to the Pier Cloud platform via Python, Node.js, or cURL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design well-structured agent loops with best-practice coaching and cross-model review gates before you run them. Use when the user wants to design, build, or set up an agent loop, iterative agent workflow, self-review loop, LLM-as-judge loop, multi-model council, reviewer/judge gate, or goal-driven looping process. Guides goal refinement, typed verification criteria, reviewer/judge selection, privacy boundaries, termination guards, and observability, then emits a RUN_IN_SESSION.md handoff prompt plus portable loop.yaml, loop.resolved.json, LOOP.md, and run-loop.py.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sub-skill de agent-ready-cloudflare: Implement llms-full.txt
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sub-skill de agent-ready-cloudflare: Implement ACP Discovery Document
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an "enable observability" card asks for metrics, traces or logs - what the developer task must add per language (Go, Node/TS, Python, Java/Kotlin, .NET, Ruby, PHP), the zero-code agents, the OTEL_* environment variables and resource attributes, and how to reach GCP, AWS, Vercel or a plain OTLP endpoint
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an "enable observability" card targets self_hosted - a minimal Grafana LGTM stack (Loki, Grafana, Tempo, Mimir or Prometheus, with Alloy or an OpenTelemetry Collector) by docker-compose or Helm, its resources and retention, and adding it back as TaskTrooper data sources
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an "enable observability" card asks for queues, or a worker's queue.backlog / consumer lag signals are unbound - which exporter or direct broker data source reads Kafka, RabbitMQ, NATS and Redis queues, the metric names the recipes expect, and the consumer-side metrics the developer adds
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an "enable observability" card asks for rum on a frontend, or web.* signals are unbound - how the developer collects Core Web Vitals and page views (web-vitals to the app's own endpoint as log lines, or Sentry / PostHog), what each event must carry, and what stays out of it
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the diff adds, upgrades, re-sources or re-pins a dependency - manifests, lockfiles, go.mod replace, Docker base images, GitHub Actions uses, Terraform modules, submodules, vendored or generated code, curl-pipe-sh installs - or changes what goes into a package or image, how releases are signed and verified, or how an updater or plugin loader trusts what it installs
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a model is served online (FastAPI, BentoML) or scored in batch, when changing how a model artifact is loaded or versioned, or when adding drift, quality or prediction monitoring and a rollout plan for a new model
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when ordering board tasks - set priority/blocked_by/deploy_depends_on by severity and dependency, split MoSCoW within a feature, and use RICE/ICE only for a genuine "what next" call across several features
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need the end-to-end merge -> deploy -> watch -> verdict sequence for a delivery mode, or a tool result you did not expect (refusal, park, tag exists)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a release reaches awaiting_verdict (or you are woken for an incident) - how to read runtime logs, error groups, health and smoke evidence for the release's component and decide finish, re-check, roll back or hand to a human
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a mobile app needs a release pipeline - fastlane GitHub Actions to TestFlight (iOS) and Play internal track (Android), with code signing and the release naming that maps to TaskTrooper's prod deploy
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a web/frontend app needs a cloud deploy - GitHub Actions to Cloud Run/ECS for SSR or GCS+CDN/Firebase and S3+CloudFront for static, with build-time env and cache invalidation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Built-in deploy recipes and deploy targets. Use when a task asks you to set up or change a stage/preprod/prod deploy workflow, including the system's "Set up <env> deploy" tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a backend or worker service needs a cloud deploy - container-first GitHub Actions deploys to Google Cloud Run (WIF) or AWS ECS/App Runner (OIDC), with migrate-before-deploy and a health-check gate
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding logging to Go code - the repository's logger with structured fields, request-scoped correlation, correct levels, no secrets or double-logging
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Skill Base server deployment guide. Covers starting the Skill Base server (npx skill-base), Docker configuration, port mapping, SQLite database backup, and platform capabilities (collections, tags, GitHub import). For deploying and operating the Skill Base platform itself only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.