AWS Agentic AI
zxkane/aws-skills
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.
Maps the W3TCQA AWS test matrix (orchestrator ~/ci, EC2 boxes, /share paths, report artifacts, box naming, log formats).
Install Analyze W3tcqa Environment
$ npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BoldGrid/w3-total-cache analyze-w3tcqa-environment --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BoldGrid/w3-total-cache.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/analyze-w3tcqa-environment .claude/skills/analyze-w3tcqa-environment && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyze-w3tcqa-environment" agent skill from https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environment into .claude/skills/analyze-w3tcqa-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-w3tcqa-environment", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BoldGrid/w3-total-cache analyze-w3tcqa-environment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BoldGrid/w3-total-cache.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/analyze-w3tcqa-environment .agents/skills/analyze-w3tcqa-environment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-w3tcqa-environment" agent skill from https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environment into .agents/skills/analyze-w3tcqa-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-w3tcqa-environment", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BoldGrid/w3-total-cache analyze-w3tcqa-environment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BoldGrid/w3-total-cache.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/analyze-w3tcqa-environment .cursor/skills/analyze-w3tcqa-environment && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyze-w3tcqa-environment" agent skill from https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environment into .cursor/skills/analyze-w3tcqa-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-w3tcqa-environment", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BoldGrid/w3-total-cache.git --path .claude/skills/analyze-w3tcqa-environment--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BoldGrid/w3-total-cache analyze-w3tcqa-environment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BoldGrid/w3-total-cache.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/analyze-w3tcqa-environment .gemini/skills/analyze-w3tcqa-environment && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyze-w3tcqa-environment" agent skill from https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environment into .gemini/skills/analyze-w3tcqa-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-w3tcqa-environment", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BoldGrid/w3-total-cache analyze-w3tcqa-environmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BoldGrid/w3-total-cache.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/analyze-w3tcqa-environment .github/skills/analyze-w3tcqa-environment && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyze-w3tcqa-environment" agent skill from https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environment into .github/skills/analyze-w3tcqa-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-w3tcqa-environment", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BoldGrid/w3-total-cache analyze-w3tcqa-environment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BoldGrid/w3-total-cache.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/analyze-w3tcqa-environment .opencode/skills/analyze-w3tcqa-environment && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyze-w3tcqa-environment" agent skill from https://github.com/BoldGrid/w3-total-cache/tree/master/.claude/skills/analyze-w3tcqa-environment into .opencode/skills/analyze-w3tcqa-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-w3tcqa-environment", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyze-w3tcqa-environment- GitHub stars
- 166
- Token cost
- ~2.1k tokens
- SKILL.md length
- 777 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- GPL-2.0
At a glance
Maps the W3TCQA AWS test matrix (orchestrator ~/ci, EC2 boxes, /share paths, report artifacts, box naming, log formats).
- Works in 6 steps: Locate artifacts → Parse summary.html → Compare pass vs fail on same box → …
- Analyzing AWS QA failures
- SKILL.md covers Quick orientation, When to read this skill, Analysis workflow and Failure mode taxonomy, plus 3 more sections
- Runs Shell scripts from its folder; calls git
What it does
Analyze W3tcqa Environment is an agent skill from BoldGrid/w3-total-cache. Maps the W3TCQA AWS test matrix (orchestrator ~/ci, EC2 boxes, /share paths, report artifacts, box naming, log formats). Use when analyzing AWS QA failures, uploaded w3tcqa-ci.zip bundles, summary.html, per-box logs, restore-final state, or planning fixes to qa/plugins probe scripts.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `IMPLEMENTATION-PLANS.md`, `REFERENCE.md` and `scripts/summary-spec-counts.sh`).
It sits in Agent Workflows. It works with Amazon Web Services. The licence is GPL-2.0.
When your agent uses it
- Analyzing AWS QA failures
- Uploaded w3tcqa-ci.zip bundles
- Restore-final state
- Planning fixes to qa/plugins probe scripts
Example prompts
- “/analyze-w3tcqa-environment”
Requirements
- A Bash shell
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 99a8bbc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyze W3tcqa Environment loads about 2.1k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 777 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from BoldGrid/w3-total-cache at commit 99a8bbc, republished under its GPL-2.0 licence (© BoldGrid). 777 words, ~2,133 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-w3tcqa-environment/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- analyze-w3tcqa-environment
- description
- Maps the W3TCQA AWS test matrix (orchestrator ~/ci, EC2 boxes, /share paths, report artifacts, box naming, log formats). Use when analyzing AWS QA failures, uploaded w3tcqa-ci.zip bundles, summary.html, per-box logs, restore-final state, or planning fixes to qa/plugins probe scripts.
Analyze W3TCQA environment
W3TCQA runs Mocha/Puppeteer specs across a matrix of EC2 boxes (HTTP server × PHP × WordPress layout × cache engine). This skill orients agents on where code lives, how artifacts are named, and how to triage failures without re-deriving the layout each time.
Quick orientation
| Layer | Typical path | Role |
|---|---|---|
| Orchestrator repo | ~/ci/ on controller EC2 (= qa/env/ in the plugin repo) | Spawn boxes, upload plugin zip to S3, collect logs, build summary.html |
| Plugin under test | qa/env/working/w3tc/ (orchestrator) → S3 zip → /share/w3tc/ (box) | Branch built and mounted into WordPress |
| Test specs | qa/tests/**/*.js → on box: /root/w3tcqa/ (symlink to qa/tests) | Mocha tests |
| Box scripts | qa/env/scripts/ → on box: /share/scripts/ | Init, restore, w3test, batch-test |
| Per-subenv vars | boxes/{box}/environments/*.sh → /share/environments/ | W3D_* exports for each matrix cell |
| Reports (orchestrator) | qa/env/working/reports/{box}/*.log | Collected after each run |
| Reports (by test) | qa/env/working/reports-by-test/{spec}/{pass|fail}-{box}@{subenv} | Copied by 800-report-generate |
Uploaded w3tcqa-ci.zip artifacts are usually the orchestrator's full plugin clone at top-level ci/ (same tree as GitHub w3-total-cache) plus ci/qa/env/working/ report outputs from one run. They do not include live box disks (backup-final-wp-sandbox, MySQL dumps).
For path maps, box naming, log markers, and orchestration flow details, see REFERENCE.md.
For parallel fix tracks (QA probes, Disk Enhanced, isolated failures), see IMPLEMENTATION-PLANS.md.
When to read this skill
- User uploaded
w3tcqa-ci.zip,summary.html, or per-box log ZIPs - Triaging AWS matrix failures (
20260610w-AWS-testing.txtstyle summaries) - Questions about
~/ci/,/share/w3tc,restore-final, orW3D_*variables - Planning changes to
qa/plugins/*.phpprobe scripts vs plugin cache keys - Correlating footer-pass vs probe-fail patterns on the same box
Analysis workflow
Copy this checklist and tick as you go:
W3TCQA triage:
- [ ] Identify artifact type (summary only | full ci zip | single-box logs | live box)
- [ ] List failing spec families from summary.html (grep ^<p> or spec headings)
- [ ] Sample one fail log + one pass log on same box/spec family
- [ ] Classify failure mode (probe | rewrite | setOptions | env corruption | skip)
- [ ] Check plugin revision (git log / commit in ci zip)
- [ ] Note box dimensions (apache vs nginx, file_generic, https, subdomain, etc.)
- [ ] Draft fix owner (qa probe | plugin pgcache | env script | flaky retry)Step 1 — Locate artifacts
| User provided | Open first |
|---|---|
w3tcqa-ci.zip | Extract to .cursor/working/{date}-w3tcqa-ci/; read ci/qa/env/working/reports/summary.html |
summary.html / pasted HTML | `grep -E '^[a-z] |
{box}-{NN}.zip | Per-worker logs from one box; unzip under apache-php74-wp69-single-zips/ |
Single .log | Parse `testResultFailed |
Orchestrator log filename pattern:
{spec-path-with-slash-as-dash}@{subenvironment}.log
Example: pagecache/basic.js + blog-0-pagecache-file → pagecache-basic@blog-0-pagecache-file.log
Step 2 — Parse summary.html
- Each
<p>block is a spec family (dirname + test file stem, slashes → hyphens in logs). - Each
<li>is one environment run:{box} {subenv}with link to log. - Failure count ≈ number of
<li>under failed specs (plusnone-executedif a box produced no logs).
Generate a spec failure histogram:
grep '^<p>' summary.html | sed 's/<[^>]*>//g' | grep -v '^$'Step 3 — Compare pass vs fail on same box
High-signal pattern (page-cache regressions):
| Often passes | Often fails | Implication |
|---|---|---|
pagecache/cache-hit-single-footer | pagecache/basic | Browser footer OK; qa/plugins/cache-entry.php probe cannot read backend entry |
pagecache/change-post | browsercache/compression | Caching works in browser; compression.php backend lookup wrong |
pagecache/user-roles | generic/user-agent-groups | Footer checks OK; user-agent-groups.php probe keys wrong |
If both footer and probe fail, suspect pgcache not writing (drop-in, rules, reject reason) before probe key mismatch.
Step 4 — Read a fail log structure
Typical sections (top to bottom):
Restore wp state - to final—restore-final.rbresetRestarting http server— source mount or rules changeset options— Puppeteer admin save + DOM verification- Mocha assertion or
testResultFailedmarker
Log outcome markers (written by w3test):
| Marker | Meaning |
|---|---|
testResultPassed | Spec completed success |
testResultFailed | Assertion or hook failure |
testResultSkipped | Environment filter excluded run |
Probe failures often show checking wp.… (from cache-entry.php line 46) without Page Caching using … in the body → miss path or wrong cache key.
Show full SKILL.md (271 more words)Show less
Step 5 — Map box name to dimensions
Box slug pattern: {http}-{php}{-port|-https?}-{wp-layout}[-{variant}]
Examples:
apache-php74-wp69-single— Apache, PHP 7.4, WP 6.9, single site, port 80nginx-php85-wp71-pathwp-subdir— nginx, PHP 8.5, WP in/wp/subdir multisiteapache-php85-https-wp71-subdomain— HTTPS, subdomain multisite
Subenvironment suffix (after @ in log name): {blog}-{pagecache|cache}-{engine}
Examples: blog-0-pagecache-file, blog-1-pagecache-redis, blog-2-cache-memcached
Parse boxes/{box}/environments/*.sh in the repo (or ci/qa/env/boxes/ in a zip if present) for exact W3D_* values.
Step 6 — Correlate with plugin revision
On orchestrator or in ci/ zip:
git log -1 --oneline
git branch -vBoxes run whatever was in working/w3tc.zip at upload time (350-upload-w3tc), fetched to /share/w3tc.zip during box.init.
Failure mode taxonomy
Use this to split work across agents:
| Mode | Symptoms | First files |
|---|---|---|
| Backend probe | pageCacheEntryChange, plain not found, user-agent-groups error | qa/plugins/cache-entry.php, compression.php, user-agent-groups.php |
| Disk Enhanced / rewrite | w3tc_php: executed, missing page_enhanced/*.html | PgCache_Environment.php, Apache htaccess templates, accept-qs.js |
| Admin / setOptions | failed to find _wpnonce, wizard not skipped | qa/lib/w3tc.js, setup guide state in backup-final |
| Box state corruption | Dispatcher not found in db.php, ERR_CONNECTION_REFUSED, mysql errors mid-spec | restore-final.rb, w3tc-mount.sh, engine flip tests (generic/options) |
| Flaky / infra | pass on retry, boxValidSuccess missing, SSH timeout | 400-run-tests retry loop, AWS AMI |
Orchestrator commands (reference)
Run from qa/env/ on controller (paths relative to that directory):
| Script | Purpose |
|---|---|
./100-generate-envs | Regenerate amis/, boxes/ descriptors |
./w3tc-clone | Clone plugin into working/w3tc |
./350-upload-w3tc | Zip + S3 upload; writes working/w3tc_zip_url.yml |
./400-run-tests N M | N parallel box instances, M threads |
./800-report-generate | Build working/reports/summary.html |
./900-report-send | Email report |
Scratch file convention
When triaging a run, prefix scratch files per AGENTS.md:
- Full CI zip:
20260610w-w3tcqa-ci-summary-notes.md - Single spec:
ENG7-XXXX-w3tcqa-pagecache-basic-triage.md(if Jira-linked)
Store under .cursor/working/, not /tmp/.
Additional resources
- REFERENCE.md — full path map, mount lifecycle,
W3D_*index, zip layouts - IMPLEMENTATION-PLANS.md — parallel agent work packages for common fix tracks
scripts/summary-spec-counts.sh— failure histogram fromsummary.html
© BoldGrid, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in .claude/skills/analyze-w3tcqa-environment of BoldGrid/w3-total-cache.
- SKILL.md
- IMPLEMENTATION-PLANS.md
- REFERENCE.md
- scripts/summary-spec-counts.sh
Open the folder on GitHubat commit 99a8bbc
Compare with similar skills
Analyze W3tcqa Environment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyze W3tcqa Environment this skillBoldGrid/w3-total-cache | 166 | — | ~2.1k | Automated safety check: Pass | GPL-2.0 | |
| AWS Agentic AIzxkane/aws-skills | 367 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Mobileminorun365/html-share | 108 | — | ~662 | Automated safety check: Pass | Apache-2.0 | |
| Cao Agent Routingawslabs/cli-agent-orchestrator | 1.4k | — | ~552 | Automated safety check: Pass | Apache-2.0 | |
| AWS MCP Setupzxkane/aws-skills | 367 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cao Session Managementawslabs/cli-agent-orchestrator | 1.4k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Mobile
minorun365/html-share
Send the current Claude Code or Codex task to HTML共有くん for phone review, then wait for approval or follow-up instructions and continue the same task.
- Official
Cao Agent Routing
awslabs/cli-agent-orchestrator
Find and select the best installed CAO agent profile for a task before delegating with assign or handoff.
AWS MCP Setup
zxkane/aws-skills
Configure AWS MCP servers for documentation search and API access.
- Official
Cao Session Management
awslabs/cli-agent-orchestrator
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions.
Check Docs
go-to-k/cdkd
Check if documentation (README.md, AGENTS.md, docs/) is up to date with recent code changes.
More from BoldGrid/w3-total-cache
Update Changelog
BoldGrid/w3-total-cache
Add or verify W3 Total Cache release changelog bullets in readme.txt and changelog.txt.
Move PR To Private Ghsa
BoldGrid/w3-total-cache
Move an in-progress public GitHub PR for a security fix into a GitHub Security Advisory's temporary private fork (TPF) so the remaining work continues privately.
Repost PR Reviews To Tpf
BoldGrid/w3-total-cache
Repost GitHub review content (Copilot bot reviews, human-reviewer threads, etc.) from a closed public PR onto its GHSA temporary-private-fork (TPF) PR, anchored to the source's originalcommitid at…
Related
Works with
Categories
Questions about Analyze W3tcqa Environment
What does Analyze W3tcqa Environment do?
Maps the W3TCQA AWS test matrix (orchestrator ~/ci, EC2 boxes, /share paths, report artifacts, box naming, log formats). Analyze W3tcqa Environment is an agent skill from BoldGrid/w3-total-cache. Maps the W3TCQA AWS test matrix (orchestrator ~/ci, EC2 boxes, /share paths, report artifacts, box naming, log formats).
When should I use Analyze W3tcqa Environment?
Analyze W3tcqa Environment fits situations like: analyzing AWS QA failures; uploaded w3tcqa-ci.zip bundles; restore-final state; planning fixes to qa/plugins probe scripts.
How do I install Analyze W3tcqa Environment in Claude Code?
Run `npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a claude-code`. Or copy the skill folder (.claude/skills/analyze-w3tcqa-environment in BoldGrid/w3-total-cache) into .claude/skills/analyze-w3tcqa-environment in your project. Claude Code loads it when a task matches its description.
How do I install Analyze W3tcqa Environment in Codex?
Run `npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a codex`. Or copy the skill folder (.claude/skills/analyze-w3tcqa-environment in BoldGrid/w3-total-cache) into .agents/skills/analyze-w3tcqa-environment in your project. Codex loads it when a task matches its description.
Can I use Analyze W3tcqa Environment in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BoldGrid/w3-total-cache --skill analyze-w3tcqa-environment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-w3tcqa-environment, .gemini/skills/analyze-w3tcqa-environment, .github/skills/analyze-w3tcqa-environment and .opencode/skills/analyze-w3tcqa-environment in your project.
What does Analyze W3tcqa Environment need to run?
Going by SKILL.md and its folder, Analyze W3tcqa Environment needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.
Does Analyze W3tcqa Environment access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Analyze W3tcqa Environment safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Analyze W3tcqa Environment use?
Analyze W3tcqa Environment is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyze W3tcqa Environment use?
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyze W3tcqa Environment?
Skills that share tags, products or a category with Analyze W3tcqa Environment: AWS Agentic AI (zxkane/aws-skills, 367 stars), Mobile (minorun365/html-share, 108 stars), Cao Agent Routing (awslabs/cli-agent-orchestrator, 1.4k stars) and AWS MCP Setup (zxkane/aws-skills, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze W3tcqa Environment?
BoldGrid (a GitHub organization) maintains it in BoldGrid/w3-total-cache, which has 166 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: BoldGrid/w3-total-cache on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.