* improve: enhance academic-researcher based on automated review
- Add Output Delivery section instructing writes to academic-research.md so research-synthesizer can discover it
- Rewrite description with <example>/<commentary> blocks matching sibling deep-research-team agents
- Add Preferred Sources & APIs guidance (Semantic Scholar, OpenAlex, Crossref, PubMed E-utilities, arXiv API) and require DOI/arXiv ID/PMID preservation
- Add structured JSON output block (claims, seminal_works, quality_flags, research_gaps) for pipeline consistency
- Add lightweight PRISMA-inspired Systematic Review Protocol subsection
- Add retraction/predatory-journal screening to the quality-check step
- Add explicit Citation format line
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: use YAML block scalar for academic-researcher description
Unquoted plain-scalar description contained colon-space sequences
(Context:, user:, assistant:) inside the <example> blocks, which
js-yaml parses as invalid nested mapping entries. Switching to a
block scalar (>-) preserves the content verbatim while keeping the
frontmatter valid YAML.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Usq1CFqiz6Kk1X9huJNM7P
* fix: use valid JSON literals in academic-researcher output example
Replace the type-placeholder tokens (`number`, `high|medium|low`)
in the example JSON block with concrete literal values so the
block is valid, parseable JSON if copied verbatim.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Usq1CFqiz6Kk1X9huJNM7P
* fix: mark academic-researcher JSON sample values as illustrative
Address follow-up review feedback: valid-but-concrete sample values
(25, "high") could be mistaken for required output rather than
placeholders. Add an explicit "do not copy verbatim" instruction
directly above the block.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Usq1CFqiz6Kk1X9huJNM7P
---------
Co-authored-by: Claude <noreply@anthropic.com>
* improve: enhance api-designer based on automated review
- Add real gRPC/protobuf service design coverage (proto example, service checklist, service.proto deliverable) to match the agent's advertised REST/GraphQL/gRPC scope
- Adopt RFC 9457 Problem Details for REST error responses, replacing the bespoke ApiError schema
- Update target spec version from OpenAPI 3.1 to OpenAPI 3.2, noting new streaming/SSE, additionalOperations, and OAuth2 Device Flow capabilities
- Add machine-readable/AI-agent discoverability guidance (predictable spec path, llms.txt/agents.json)
- Bring rate-limiting header guidance to parity with api-architect (RateLimit/RateLimit-Policy alongside Retry-After)
- Add permissionMode: acceptEdits and missing cross-agent references (graphql-architect, graphql-security-specialist, graphql-performance-optimizer)
- Pin Apollo Federation 2.10+ with required @link directive; reference AsyncAPI 3.0 for webhook specs
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: correct protobuf field-deprecation guidance in api-designer
A field number cannot be simultaneously declared (even as deprecated)
and listed in `reserved` - protoc rejects that. Clarify the two valid
patterns: keep a deprecated field's number declared, or reserve the
number only after removing the field entirely.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QAafnmzU8wyRwuyjr7hGg9
* fix: correct RFC 9457 ProblemDetails schema in api-designer example
Per RFC 9457 §3.1, all Problem Details members are optional (drop the
`required` constraint), and `type`/`instance` should use format
`uri-reference` since relative references like `/v1/transactions/abc123`
are valid but not valid absolute `uri` values.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QAafnmzU8wyRwuyjr7hGg9
---------
Co-authored-by: Claude <noreply@anthropic.com>
Walks through combining two PreToolUse hooks with the secrets-management
skill to block leaked credentials and enforce Conventional Commits
automatically, with an AI-generated cover image.
Claude-Session: https://claude.ai/code/session_01XUj1WK4MLpuMf8xC2mbrhr
Co-authored-by: Claude <noreply@anthropic.com>
- Add missing model: sonnet frontmatter field (required by component-reviewer)
- Remove fabricated example metrics from progress tracking and delivery notification templates
- Add human-in-the-loop guidance to ask user for real scope/budget/timeline inputs
- Add Human-in-the-Loop Pause Criteria section
- Drop legacy query-context-manager/JSON requesting_agent protocol
- Consolidate generic keyword lists into a Core Practices section (RAID log, RACI matrix, CPM, EVM/SPI/CPI)
- Add How This Differs From Related Agents section
- Reword checklist items as targets to evaluate rather than pre-asserted facts
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
* feat(mcps): add Sicex trade intelligence MCP server
Adds Sicex (sicex.com) as a remote MCP under components/mcps/web-data —
customs import/export and maritime shipment data for Latin American
markets, served over Streamable HTTP with OAuth 2.1 auth.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix(mcps): correct Sicex MCP coverage description
Data coverage isn't Latin-America-only — it spans the Americas, the
full European Union, and several Asian markets. Update the description
to match.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
* Add repo-publication-auditor to security agents
The security category has agents for vulnerabilities, compliance, pen testing and
supply chain. None covers the one-time, irreversible act of making a repository
public, which fails in ways a vulnerability audit does not look for. git/
commit-guardian is adjacent but per-commit and staged-files only; this is the
whole history at the moment of publication.
Every check came out of a real mistake rather than a checklist:
- The history is the artifact. Auditing git status misses a secret removed in a
later commit, and .gitignore added after the fact never untracks anything.
- GitHub attributes a commit by the email in the commit object, so a repository
can publish an employer on every line of its contribution graph. The agent
reports the count, because 665 of 673 commits is a different decision from 2.
- Push protection treats an invented credential exactly like a real one, and
partner scanning forwards an AKIA string to the vendor within minutes. So the
agent recommends placeholders plus a seeded generator rather than telling an
owner to weaken a redaction-test fixture.
- A README number measured in the author's working copy can be measuring
something else, because tools that resolve a project root by walking up find
the outer repository when a project sits inside one. The agent re-runs the
README's own commands in a fresh clone.
Every shell command in it was run before being written down, against real
repositories, and each found real instances.
One file. The components catalog JSONs are regenerated by update-json-data.yml
on a schedule, so they are deliberately not hand-edited here.
* fix(repo-publication-auditor): the Windows path grep never matched, and the history sweep had no command
Both findings came from review on davila7/claude-code-templates#820 and
both reproduce.
C:\\\\Users\\\\ in an ERE is two literal backslashes, so it matched only an
already-escaped path and missed the real C:\Users\name it exists to
find. Using \\+ catches one backslash or several, so a raw path and a
JSON-escaped one both hit. Verified against a fixture holding both forms,
and against C:/Users and CUsers for false positives.
"Run these against the history too" named no command, which left the
agent to improvise its central check. The credential greps read the
checkout only, and a key deleted in a later commit is still served by the
API — so a tree-only scan calls a leaking repository clean. Added the
git grep form over git rev-list --all, with the output shape and an
explicit note to state when a sweep was scoped rather than full.
Verified by extracting the file's own bash blocks and running them: in a
repo whose first commit holds an AWS key and whose second removes it, the
tree scan is silent and the history scan returns the commit.
* fix(repo-publication-auditor): the history sweep dropped a pattern and did not run under zsh
Three faults in the block added by the previous commit, two found in
review and the third by running it.
The database-URL grep exists in the tree scan and was missing from the
history sweep, so a postgres/mysql/mongodb URL with embedded credentials
was caught in the checkout and missed once removed — the one case the
history sweep exists for.
git grep ... $REVS relies on the shell word-splitting an unquoted
variable. zsh, the macOS default, does not: git receives the entire list
as a single argument and fails with 'unable to resolve revision'. The
command did not work at all on the platform most likely to run it, which
review could not see because reviewers read bash semantics. On a large
enough repository the bash form then overruns ARG_MAX, which was the P2.
Piping through xargs -n 200 fixes both.
The revisions must not be followed by -- <path>: xargs appends them last,
and anything after -- is read as a path, which silently turns the sweep
back into a working-tree scan with no error and no commit prefix. Removed
the suggestion to scope it that way and said why.
Verified under zsh against a repo whose first commit holds an AWS key and
a postgres URL and whose second removes both: the tree scan is silent and
the history sweep returns the commit for each.
* improve: enhance adr-generator based on automated review
- Fix absolute-path bug: docs/adr/ was written with a leading slash
(filesystem-root-absolute); now explicitly repo-root-relative
- Rewrite description with trigger phrases and 3 <example> blocks to
drive automatic subagent delegation, matching postgres-pro/api-documenter
- Add explicit model: sonnet field (required by component-reviewer)
- Fix ambiguous ALT-XXX coding scheme: each alternative now gets one
stable ALT-NNN code reused for Description and Rejection Reason
- Add workflow step to cross-reference and cross-link existing/superseded
ADRs (search docs/adr/, update superseded ADR's status/superseded_by)
- Narrow tools: drop unused Bash, keep Read/Grep/Glob/Edit/Write
- Add Decision Drivers section (MADR-style) and a grounding instruction
to verify claims against the real repository state
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: correct YAML newline escaping and supersedes step ordering
Addresses cubic review findings on PR #829:
- description frontmatter used doubled \\n instead of \n, so the
YAML double-quoted scalar rendered literal backslash-n text
instead of real newlines between the <example> blocks
- Step 2.5 set the new ADR's supersedes field before the new ADR
file existed (it's only created in Step 3); moved that to Step 3
and kept only the old ADR's Edit update in Step 2.5
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KNoo8usoppzPaZkETzVo3R
* fix: use file-relative path in ADR cross-reference example
Addresses a greptile review finding on PR #829: the example
References link used docs/adr/adr-0003-....md, which resolves
under docs/adr/docs/adr/ since ADRs already live in that directory
— a broken link. Use ./adr-0003-....md (relative to the generated
ADR file) instead.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KNoo8usoppzPaZkETzVo3R
* fix: resolve NNNN/MMMM placeholder collision in supersession steps
Addresses a cubic review finding on PR #829: NNNN means "this ADR's
own number" everywhere else in the doc, but Step 3 used it to mean
the superseded ADR's number while Step 2.5 called the new ADR's own
number MMMM instead — risking self-supersession or a mis-filled
superseded_by. Step 2.5 now consistently uses NNNN for the new ADR's
own number; Step 3 uses a distinct OLD placeholder for the
superseded ADR's number.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KNoo8usoppzPaZkETzVo3R
---------
Co-authored-by: Claude <noreply@anthropic.com>
* improve: enhance computer-vision-engineer based on automated review
- Fix deprecated TensorRT 10.x API (build_serialized_network, set_memory_pool_limit)
- Add Foundation & Zero-Shot Vision Models section (SAM2/SAM3, Grounding DINO,
CLIP, Florence-2, multimodal LLMs) with a model selection framework
- Update default detector to YOLO11 with AGPL-3.0 licensing note and
RT-DETRv2/RF-DETR alternatives
- Modernize face recognition guidance to InsightFace/DeepFace, keep dlib
face_recognition as a lightweight fallback only
- Add multi-object tracking (ByteTrack via model.track) to video analysis
- Replace unimplemented document-structure stub methods with a layoutparser-based
approach and pointers to unstructured/VLM alternatives
- Add a Compliance & Ethical Considerations section for biometric/PII data
- Align frontmatter/structure with sibling data-ai agents: add model: sonnet,
Glob/Grep tools, multi-example description, and an Integration with Other
Agents section with explicit boundaries vs ai-engineer and ml-engineer
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: reset ByteTrack state between independent video streams
Reusing a VideoAnalyzer instance for a new stream would otherwise carry
stale track IDs from the previous session, since persist=True caches
tracker state on the model's predictor.
Addresses review feedback on PR #821.
* fix: stop prior stream's threads before starting a new one
start_real_time_analysis previously only reset tracker state but left
any earlier capture/process threads running against the same
frame_queue/result_queue/model, so a reused VideoAnalyzer instance could
mix frames and tracker state across streams. Add stop_processing() to
join the old threads and drain the queues before starting a new stream.
Addresses further review feedback on PR #821.
* fix: correct layoutparser color channel and text-region filter
- Convert BGR (cv2.imread) to RGB before Detectron2LayoutModel.detect(),
since PubLayNet was trained on RGB
- Include PubLayNet's 'Title' and 'List' labels in text_regions, not
just 'Text', so headings and list blocks aren't dropped
Addresses cubic review feedback on PR #821.
* fix: unblock capture thread on stop and fail loudly if it won't die
cap.read() blocks until a frame arrives, so join(timeout=5.0) alone
could return with the capture thread still alive and start_real_time_analysis
would then reuse the shared model/queues underneath it. stop_processing
now releases the VideoCapture to unblock read() immediately, and raises
if a thread still hasn't exited after the join timeout instead of
silently proceeding.
Addresses further greptile review feedback on PR #821.
* fix: re-check thread liveness on retry instead of the processing flag
stop_processing() sets self.processing = False before it can guarantee
the old threads have exited (e.g. one is still blocked in model.track()
past the join timeout and it raises). A caller retrying
start_real_time_analysis after that RuntimeError would see
self.processing already False and skip straight to relaunch, letting
the still-alive worker resume against the shared model/queues once it
unblocks. Guard on actual thread.is_alive() instead so a retry keeps
re-joining until the old threads are confirmed dead.
Addresses further greptile review feedback on PR #821.
* fix: call stop_processing unconditionally to always drain queues
Gating stop_processing() on thread liveness skipped the queue drain
whenever the previous call's stuck thread had exited by the time of a
retry (the liveness check would then be False), leaking stale
frames/results from the old stream into the new one. stop_processing is
idempotent for dead/None threads, so call it unconditionally instead.
Addresses cubic review feedback on PR #821.
* fix: guard tracker reset against predictor without trackers attribute
Ultralytics only registers .trackers on the predictor once model.track()
has run at least once. If this model instance was previously used with
model.predict()/model() (plain inference, no tracking), self.model.predictor
exists but lacks a trackers attribute, so the direct attribute access
raised AttributeError and aborted stream startup. Use getattr with a
default instead of assuming the attribute exists.
Addresses further greptile review feedback on PR #821.
---------
Co-authored-by: Claude <noreply@anthropic.com>
Regenerate docs/components.json and dashboard public artifacts to pick up
new components (livetennisapi MCP, open-banking-io skill) and refreshed
download stats.
- doordash-group-orders: quote description (contains ": ")
- ray-data, ray-train: quote `ray[data]` / `ray[train]` inside the
dependencies flow sequence (nested brackets are invalid there)
- motion-canvas: quote `@motion-canvas/*` dependency entries (`@` is a
reserved indicator and cannot start a plain scalar)
- agirails-agent-payments: drop a stray leading `+` on the description
line left over from a diff paste
- scholar-evaluation: add missing frontmatter (name + description taken
from the existing Overview paragraph)
All six were skipped by `npx skills add davila7/claude-code-templates`;
verified 0 skipped after this change.
Co-authored-by: cj <cj-ant@users.noreply.github.com>
* improve: enhance data-analyst based on automated review
- Add missing model field (sonnet)
- Add clarifying-questions preamble before starting analysis
- Fix stale Data Studio reference to Looker Studio
- Ground vague concept lists with concrete tools & libraries
- Add Responsible Analysis section for data privacy/governance
- Remove stray duplicate blank line
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: address cubic review findings on data-analyst
- Remove orphaned Communication Protocol / Analysis Context block
(get_analysis_context) left dangling after the "Query context manager"
step was replaced by the clarifying-questions preamble; the reference
sibling data-scientist.md has no equivalent block either.
- Drop the duplicated tool-name parenthetical on "Business intelligence"
now that the same names live in the single "Tools & libraries" list.
Co-Authored-By: Claude Code <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
There is no cost or FinOps MCP in the catalog today. nable answers spend
questions across AWS, Azure, GCP, Kubernetes and 15+ SaaS and AI
providers, and drafts the Terraform fix as a pull request a human
reviews.
Runs with uvx, like the nine existing uvx components. Needs no API key
in the config: it reads the cloud credentials already on the machine.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
* improve: enhance accessibility-tester agent based on automated review
- Fix pa11y guidance to use --runner axe (default htmlcs runner is WCAG 2.0-era, misses 2.1/2.2 violations)
- Note axe-core version requirement (>=4.5) for reliable WCAG 2.2 rule coverage
- Annotate which WCAG 2.2 new criteria are actually automatable (only 2.5.8 via axe-core target-size)
- Add a fully worked example finding to anchor severity/remediation phrasing
- Add document/PDF accessibility checklist item (Section 508/EAA scope)
- Add forced-colors / prefers-contrast manual checklist item
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: cover prefers-contrast alongside forced-colors in accessibility-tester
Addresses review feedback on PR #814 — the manual checklist tested
Windows High Contrast (forced-colors) but omitted the distinct
prefers-contrast media feature, which interfaces can also use for
alternate high-contrast styling.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QTTuf1dEt7QW83eyAPV7Lm
* fix: require both forced-colors and prefers-contrast checks explicitly
The previous wording used "or", allowing an audit to satisfy the
checklist item by testing only one of the two distinct contrast
display modes.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QTTuf1dEt7QW83eyAPV7Lm
* fix: correct pa11y WCAG 2.2 coverage claim and axe-core version check scope
pa11y's axe runner maps WCAG2AA to wcag2a/wcag21a/wcag2aa/wcag21aa tags
only (confirmed against pa11y/pa11y#666 and lib/runners/axe.js) — it does
not include wcag22aa, and pa11y has no --tags CLI flag. Also scope the
axe-core version check to the tool actually being run, since
@axe-core/cli --version only reports its own bundled axe-core, not
pa11y's or @axe-core/playwright's independently-resolved versions.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QTTuf1dEt7QW83eyAPV7Lm
* fix: give a concrete command for checking per-tool axe-core versions
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QTTuf1dEt7QW83eyAPV7Lm
---------
Co-authored-by: Claude <noreply@anthropic.com>
* improve: enhance model-evaluator based on automated review
- De-anchor hardcoded/aging model names (GPT-4o, Gemini 1.5, etc.) in
frontmatter examples and Model Categories, replacing them with
capability-tier language and a prominent instruction to verify
current model IDs via WebSearch/WebFetch before recommending or
testing
- Add a "Required Initial Step: Requirements Gathering" section,
matching the pattern used by sibling agents llm-architect and
prompt-engineer
- Add WebFetch to the tools list for pulling full pricing/leaderboard
pages (LMSYS Arena, HELM) beyond WebSearch snippets
- Add Inspect AI and OpenAI Evals to the Standard Frameworks & Tools
table
- Fix imprecise terminology: replace "GitHub Copilot" (a product, not
a benchmarkable model) with actual code-specialized models, and
clarify "Vision" models are a native capability rather than a
separate SKU
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: align tier language in model-evaluator example
The first description example's Context named balanced/flagship tiers
but the assistant response evaluated budget/balanced tiers instead.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FHagP9k8UdbMyPJHjmYaTy
---------
Co-authored-by: Claude <noreply@anthropic.com>
* improve: enhance prompt-engineer based on automated review
- Add WebSearch to tools frontmatter, matching sibling ai-specialists agents
- Add 4th description example covering Claude Code subagent/skill prompt optimization
- Add guidance on avoiding aggressive imperative language (CRITICAL/YOU MUST/NEVER EVER) that causes overtriggering on current models
- Route target-model answer to model-specific prompting guidance (verbosity, effort calibration, delegation, tool-triggering)
- Add long-context document placement guidance (documents near top, instructions/query at end)
- Expand agentic prompting into concrete sub-guidance (tool-triggering, overeagerness containment, destructive-action confirmation, tool-error handling, autonomy boundary)
- Sharpen budget_tokens deprecation language (returns HTTP 400 on current models; effort/max_tokens is the replacement)
- Reference Structured Outputs as a response-parsing option
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: qualify budget_tokens claim by model generation, regenerate catalog
Addresses PR review feedback:
- cubic-dev-ai/greptile: dashboard/catalog artifacts were stale after the
prompt-engineer edits (old tool allowlist, 3-example description) —
regenerated via scripts/generate_components_json.py.
- cubic-dev-ai: the budget_tokens deprecation claim was overbroad — it now
varies correctly by model generation instead of asserting a blanket
HTTP 400 on all "current" models.
Co-Authored-By: Claude Code <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
* improve: enhance task-decomposition-expert based on automated review
- Trim tools allowlist to Read, Glob, Grep, WebSearch (drop unused Write/Edit/Bash)
- Add "Boundaries with Related Agents" section distinguishing from project-manager and scrum-master
- Instruct grounding the WBS in the actual codebase via Read/Glob/Grep before finalizing
- Add PERT (three-point) estimation guidance for Medium+ complexity tasks
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: address review feedback on task-decomposition-expert
- Regenerate the dashboard content mirror so it matches the trimmed
tool allowlist and new prompt sections (Greptile/cubic P2).
- Reword the Boundaries section so it no longer claims project-manager
and scrum-master appear in the Agent Handoff Plan table (cubic P3).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VZwwQ2MD4wsrwTJi5yM515
---------
Co-authored-by: Claude <noreply@anthropic.com>
* improve: enhance salesforce-expert agent based on automated review
- Add required model field (sonnet) to frontmatter
- Replace invalid tools list (vscode, execute, sfdx-mcp/*, agent, todo) with valid Claude Code tool names
- Replace generic description with routing-oriented description plus 3 <example>/<commentary> blocks
- Add Agentforce & Agent Actions subsection (exposing Apex as Agentforce Actions, Topics/Instructions, guardrails)
- Add Flow vs. Apex decision-guidance subsection
- Add Lightning Web Security (LWS) and API-version-pinning guidance to operationalize the Release Aware Developer persona
- Add Salesforce CLI Commands Reference section using the current unified sf CLI, noting sfdx is legacy
- Normalize bullet indentation to a single "- " marker
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: remove TodoWrite from salesforce-expert tools allowlist
TodoWrite isn't in StructuralValidator's accepted tool identifiers
(Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch, *), which
was flagging STRUCT_W006 on the PR.
---------
Co-authored-by: Claude <noreply@anthropic.com>
Claude