Skip to content
TrustedSkillsbeta
Back to all skills

Tinybird Deploy

Listed
pollinations·vlatest·data·MIT

Automates deployment of tiny bird models to Pollinations' infrastructure for instant sharing and experimentation.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pollinations/pollinations --skill tinybird-deploy -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pollinations

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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.europe-west2.gcp.tinybird.co.

    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.europe-west2.gcp.tinybird.coundeclared

    What it found

    • .claude/skills/tinybird-deploy/SKILL.md:113contacts api.europe-west2.gcp.tinybird.co
      curl -fsS "https://api.europe-west2.gcp.tinybird.co/v0/pipes/weekly_usage_stats.json?weeks_back=12" \

  • No credential access: failed

    Touches credential material in 4 places.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

    What it found (3 of 4)

    • .claude/skills/tinybird-deploy/SKILL.md:37OS keychain / credential manager
      TB_TOKEN="$(security find-generic-password -a "$USER" -s tinybird-staging-deploy -w)"
    • .claude/skills/tinybird-deploy/SKILL.md:39OS keychain / credential manager
      TB_TOKEN="$(security find-generic-password -a "$USER" -s tinybird-prod-deploy -w)"
    • .claude/skills/tinybird-deploy/SKILL.md:69OS keychain / credential manager
      TB_TOKEN="$(security find-generic-password -a "$USER" -s tinybird-staging-deploy -w)"

  • 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 pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pollinations/pollinations at b5bae6b280.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
b5bae6b280
Manifest
.claude/skills/tinybird-deploy/SKILL.md
Scanned
1 file, 181 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

tinybird-deploy

What it does

This skill enables AI agents to deploy applications directly to Tinybird, a serverless data streaming platform. It streamlines the process of getting data pipelines and analytics infrastructure live without manual configuration steps.

When to use it

  • Automating the deployment of real-time data streams for new analytics projects.
  • Integrating Tinybird into existing agent workflows that require immediate backend provisioning.
  • Reducing operational overhead by removing manual CLI or dashboard interactions for deployments.
  • Scaling data infrastructure rapidly across multiple environments via code execution.

Key capabilities

  • Direct deployment of Tinybird resources to production or staging environments.
  • Execution of deployment commands within the agent's runtime context.
  • Integration with the Tinybird API to manage stream lifecycles programmatically.

Example prompts

  • "Deploy my new time-series stream configuration to the Tinybird production cluster."
  • "Use tinybird-deploy to push the updated schema changes for our user activity logs."
  • "Automate the deployment of the daily aggregation pipeline to Tinybird before the end of the day."

Tips & gotchas

Ensure your AI agent has valid authentication credentials (API keys or tokens) configured before attempting a deployment, as unauthorized requests will fail. Verify that the target stream names and configurations in your code match your intended schema to prevent runtime errors after deployment.