Skip to content
cccskills
FreePublished on GitHub

debug

Investigate a vailá failure from terminal evidence and a safe reproduction; use for /debug or requests to diagnose broken GUI, CLI, file operations or downloads.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Debug vailá

Start from the symptom, expected result, command or GUI action, and affected module. Read applicable AGENTS.md and task-relevant skills. Preserve unrelated working changes.

  1. Collect only relevant context: OS, Python/environment, vailá version, sanitized command or button/fields, input shape, output location, error and repeatability. Ask only for missing information that blocks reproduction. Do not dump environment variables, authentication files, cookies, private URLs or tokens.
  2. Trace the entry point to the responsible operation. Separate parameter collection, worker execution, callbacks and outputs. State the failing invariant; distinguish observations from hypotheses.
  3. Reproduce with the smallest safe fixture. File Manager: temporary directories and --dry-run first. Downloader: simulated yt-dlp callbacks. Use --debug and optional File Manager --log-file outside selected targets when needed.
  4. Never automatically remove real user data, start a transfer or download media as diagnosis. Those actions need explicit task-specific authorization; prepare and show the exact command and effects first. Normal temporary-file tests need no additional approval.
  5. Narrow the cause with evidence. Record the reproducer and outcome before editing. If a fix is authorized, change the responsible layer and add a meaningful regression proof. Otherwise provide the concrete proposed fix with evidence.
  6. Run focused validation: python -m pytest tests/test_vaila_ytdown.py tests/test_filemanager_operations.py tests/test_filetools_downloader.py. GUI tests need a display and simulated downloads. Set VAILA_GUI_ARTIFACTS to a temporary directory when screenshots are useful.
  7. Report cause, affected behavior, changed files, exact checks/outcomes and anything unverified. Stop when the requested failure is resolved or identify concrete missing evidence.

File Manager invariants: fixed confirmed targets; no silent overwrite or output traversal; permanent removal explicitly confirmed; no worker widget calls; terminal launch distinct from transfer completion. Downloader invariants: TXT loads without starting; one active run; shared audio/video batch behavior; completion after post-processing; cooperative cancellation; nonzero status for partial failures.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard infrastructure monitoring unrelated to AI agents, or when the agent is not instrumented with OpenTelemetry (for Reliability, Cost, Safety, Security alerts). NOTE: Reliability, Cost, Safety, and Security alerts use generic OTel metrics and work across runtimes (such as Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 20, 2026

Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a specific model is deployable (`gcloud ai model-garden models list-deployment-config`), query deployment cost, troubleshoot deployment errors (like quota limits), or undeploy/clean up endpoints. Also use when copying and deploying a 1P Tuned Model. Don't use for pure listing/discovery questions of the form "is X deployed?", "list my endpoints", or "which regions have models running?" — for those use `agent-platform-endpoint-management`. Don't use for public Vertex AI deployments (use the `vertex-deploy` skill) or for running model evaluations (use the `agent-platform-eval-flywheel` skill).

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 20, 2026

Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model evaluations.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 20, 2026

Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when evaluating an agent or model, building an eval dataset, picking or writing evaluation metrics, analyzing failures, comparing results before and after a fix, or when guidance is needed on Agent Platform eval methodology — including dataset schema, LLM-as-judge scoring, and common failure causes. For fine-tuning, use agent-platform-tuning. For general production deployment, use agent-platform-deploy.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 20, 2026

Connects to and performs inference with Google Cloud Agent Platform GenAI models, including First-Party Gemini models and Third-Party OpenMaaS models (Llama, DeepSeek, Qwen, etc.). Use when asked to perform inference, ask a model a question, run a test prompt, execute chat completions, or generate code for calling Gemini or OpenMaaS models, authenticate with GenAI SDK, OpenAI SDK, or legacy Agent Platform SDK, configure base URLs and global/regional endpoints, or troubleshoot 429 Resource Exhausted (DSQ), 400 User Validation, or 404 Not Found errors. Don't use for deploying models to endpoints or for running model evaluations.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 20, 2026

Guides agents and users through migrating from Gemini API in Google AI Studio to Gemini Enterprise Agent Platform (formerly Vertex AI). Use this skill when moving applications to Google Cloud, to leverage Cloud credits, or to unify inferencing with other Cloud infrastructure (IAM, billing, telemetry).

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 20, 2026

See all skills by vaila-multimodaltoolbox

Report a problem with this skill