Infra Deploy
ListedAutomates infrastructure provisioning and deployment across multiple cloud providers using pre-defined templates and configurations.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add terrylica/cc-skills --skill infra-deploy -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
terrylica
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.cal.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.cal.comundeclaredWhat it found
- plugins/calcom-commander/skills/infra-deploy/SKILL.md:215contacts api.cal.com
curl -s -X POST "https://api.cal.com/v1/webhooks?apiKey=$CALCOM_API_KEY" \
No pipe-to-shell installers: failed
Runs code fetched at install time in 1 place.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
What it found
- plugins/calcom-commander/skills/infra-deploy/SKILL.md:206remote script piped into an interpreter
curl -s "$WEBHOOK_RELAY_URL" | python3 -m json.tool
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
Pinned to a commit: passed
Scanned terrylica/cc-skills at 3a1dc29965.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3a1dc29965
- Scanned
- 2 files, 271 lines
About this skill
What it does
This skill automates the deployment of Cal.com, a self-hosted scheduling application, to Google Cloud Run using Supabase PostgreSQL. It builds and pushes a Docker image for Cal.com and then deploys it to Cloud Run, configuring necessary environment variables from secrets stored in 1Password. The skill also supports running Cal.com locally via Docker Compose.
When to use it
- You want to quickly deploy a self-hosted instance of Cal.com to Google Cloud Run.
- You need to set up Cal.com with Supabase PostgreSQL for database management.
- You prefer deploying and managing Cal.com using Docker Compose locally.
- You're already using 1Password to manage secrets related to your Cal.com configuration.
Key capabilities
- Automated deployment of Cal.com to GCP Cloud Run.
- Integration with Supabase PostgreSQL for database hosting.
- Support for local execution via Docker Compose.
- Retrieval of secrets from a 1Password vault.
- Builds and pushes Docker images to Artifact Registry.
Example prompts
- "Deploy Cal.com to GCP Cloud Run."
- "Run Cal.com locally using Docker Compose."
- "Configure Cal.com with my Supabase database."
Tips & gotchas
- Mandatory Configuration: Requires specific environment variables (
CALCOM_GCP_PROJECT,CALCOM_GCP_ACCOUNT,CALCOM_GCP_REGION,SUPABASE_PROJECT_REF, etc.) to be set in.mise.local.tomlor 1Password. - Authentication: Requires GCP authentication configured correctly via
gcloud auth list. - API Requirements: The Cloud Run, Artifact Registry and Cloud Build APIs must be enabled on your GCP project.