skedulo-cli

Enforce tenant scoping and safe command patterns for Skedulo CLI operations.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/skeduloDevelopers/agent-skills --skill skedulo-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skedulo-cli
Source: https://github.com/skeduloDevelopers/agent-skills/tree/main/skills/skedulo-cli
Command: npx skills add https://github.com/skeduloDevelopers/agent-skills --skill skedulo-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents costly Skedulo CLI mistakes by enforcing correct tenant scoping and safe workflows for inspection, deployment, and destructive operations.

Core Features & Use Cases

  • Tenant-safe command execution: Requires -a <alias> for tenant-scoped commands to avoid deploying or querying the wrong tenant.
  • Reliable discovery and inspection: Uses --help, list --json for discovery, and get --json for inspection rather than guessing flags or structures.
  • Schema correctness via source-of-truth examples: Instructs users to fetch artifact JSON schemas from the SkeduloCLIExamples repo instead of constructing them from memory.
  • Safety for risky actions: Forces explicit confirmation before destructive operations and recommends safe deployment practices like dry-runs.

Quick Start

Run a tenant-scoped inspection safely by asking the assistant to list a specific artifact type with JSON output for tenant alias my-tenant, using the exact command pattern you expect after verifying flags with --help.

Frequently Asked Questions about skedulo-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent deploying to the wrong Skedulo Pulse tenant?

To prevent deploying to the wrong Skedulo Pulse tenant, enforce tenant scoping by always using the `-a <alias>` flag for tenant-scoped CLI commands. This ensures your deployment and inspection operations target the correct environment.

What is the safest way to inspect Skedulo CLI artifact JSON schemas?

The safest way to inspect Skedulo CLI artifact JSON schemas is to fetch them from the SkeduloCLIExamples repository. You should also use `list --json` and `get --json` commands for reliable discovery rather than guessing structures.

How do I verify Skedulo CLI command flags before running a package deployment?

Verify Skedulo CLI command flags before running a package deployment by always running `--help` first. This prevents guessing command structures and ensures you apply the correct parameters before executing deployment operations.

Can I perform a dry-run for destructive Skedulo CLI operations?

Yes, you can perform a dry-run for destructive Skedulo CLI operations. The workflow forces explicit confirmation before executing destructive actions and recommends safe deployment practices like dry-runs to prevent operational errors.

Why does my Skedulo CLI command fail when switching tenant aliases?

Skedulo CLI commands often fail when switching tenant aliases if the `-a <alias>` flag is omitted from tenant-scoped commands. Always include the alias flag and run `--help` to confirm the required parameters for tenant switching.