Skip to content
TrustedSkillsbeta
Back to all skills

Managing Astro Local Env

Checked
astronomer·vlatest·frontend·Apache-2.0

Dynamically adjusts telescope pointing & instrument settings based on local atmospheric conditions for optimal observation quality.

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 astronomer/agents --skill managing-astro-local-env -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

astronomer

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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.

  • 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 astronomer/agents at cbe1141f54.

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

Commit
cbe1141f54
Manifest
skills/managing-astro-local-env/SKILL.md
Scanned
1 file, 288 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

What it does

This skill enables an AI agent to manage local development environments for Astro projects, including setting up configurations, running servers, and handling dependencies. It provides tools for initializing new Astro projects, installing necessary packages, and ensuring a consistent development setup.

When to use it

  • You're starting a new Astro project and need help with initial configuration.
  • Your local environment is misconfigured, and you want the agent to fix it automatically.
  • You need to run or debug an Astro site locally without manual setup steps.

Key capabilities

  • Initialize new Astro projects with default configurations
  • Install required dependencies for Astro development
  • Start and stop local development servers
  • Manage environment variables for local testing

Example prompts

  • "Set up a new Astro project in this directory."
  • "Start the local development server for my Astro site."
  • "Install all missing dependencies for my Astro project."

Tips & gotchas

Ensure that Node.js and npm are installed on your system before using this skill. Some commands may require elevated permissions, so you might need to run them with sudo depending on your setup.