Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/acquia/acquia-skillsnpx agentmods add skills/acquia/acquia-skills/troubleshootingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/acquia/acquia-skills/troubleshooting)<a href="https://agentmods.dev/skills/acquia/acquia-skills/troubleshooting"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/acquia/acquia-skills/troubleshooting"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00024 | $0.02335 |
| Opus 5 | $0.00012 | $0.01167 |
| Sonnet 5 | $0.00005 | $0.00467 |
| Haiku 4.5 | $0.00002 | $0.00233 |
Grade A, and why
troubleshooting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Acquia CLI
Use when:
- Diagnosing acli authentication failures
- Resolving command errors or unexpected output
- Collecting information before contacting support
General Issues
"Command not found: acli"
Cause: The binary isn't in your system PATH.
Solutions:
# Check if it's installed
which acli
# If nothing, add to PATH
export PATH="/usr/local/bin:$PATH"
# Test
acli --version
# Make permanent (add to ~/.bashrc or ~/.zshrc)
echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
"Permission denied" when running acli
Cause: The binary isn't executable.
Solution:
chmod +x /usr/local/bin/acli
acli --version
"acli: command not found" after updating
Cause: Update didn't complete or PATH changed.
Solution:
# Reinstall
curl -fsSL https://github.com/acquia/cli/releases/latest/download/acli \
-o /usr/local/bin/acli
chmod +x /usr/local/bin/acli
# Verify
acli --version
Authentication Issues
"Error: Failed to authenticate"
Cause: Your authentication token expired or isn't valid.
Solution:
# Re-authenticate
acli auth:login
# This opens your browser to authorize again
"Error: Access Denied"
Cause: Your account doesn't have permission to access the resource.
Solutions:
-
Check you're logged in with the right account:
acli auth:me -
Verify you have access in Acquia Cloud UI:
- Go to https://cloud.acquia.com
- Check if you can see the application or resource
-
Log out and back in:
acli auth:logout acli auth:login
"Invalid JSON in credentials.json"
Cause: Credentials file is corrupted.
Solution:
# Remove the corrupted file
rm -rf ~/.acquia/cloud_api/
# Re-authenticate
acli auth:login
IDE Issues
IDE won't start
Symptoms: IDE shows "Starting..." indefinitely or won't load.
Solutions:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago Changed · +2 lines bcb530e8c549
- 10d ago First seen · 474 lines · 24 tokens per session scan F f178b5e7b565
troubleshooting is a skill published in the GitHub repository acquia/acquia-skills (9 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 2,335 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.