adding-benchmarks
Add new benchmarks to the CI pipeline. Guides through creating benchmark JSON files, integrating with bootstrap.sh, and ensuring proper CI upload via ci3.yml workflow.
Browse published AI skills maintained by AztecProtocol. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
10Repository stars across indexed skills
4,234Repository forks
5,887Average repository stars per indexed skill
423Repository stars may repeat across skills from the same repository.
Add new benchmarks to the CI pipeline. Guides through creating benchmark JSON files, integrating with bootstrap.sh, and ensuring proper CI upload via ci3.yml workflow.
Fix a failing PR by analyzing CI logs and fixing errors. Autonomous workflow that identifies failures, rebases, fixes issues, and pushes.
Rebase a PR on its base branch, fix conflicts, and verify build
Interactive debugging for failed e2e tests. Orchestrates the debugging session but delegates log reading to subagents to keep the main conversation clean. Use for ping-pong debugging sessions where you want to...
Spawn an independent Claude instance in a git worktree to work on a task in parallel. Use when the user wants to delegate a task to run independently while continuing the current conversation.
Best practices for implementing unit tests in this TypeScript monorepo. Use when writing new tests, refactoring existing tests, or fixing failing tests. Covers mocking strategies, test organization, helper func...
Investigate CI failures by following log links from ci.aztec-labs.com. Given a GitHub Actions URL, PR number, or direct CI log URL, fetch logs and recursively follow nested log links to trace the root cause of...
Guidelines for writing module READMEs that explain how a module works to developers who need to use it or understand its internals. Use when documenting a module, package, or subsystem.
Perform necessary follow-on updates as a result of updating the noir git submodule.
Updates changelog documentation for contract developers and node operators by analyzing branch changes relative to 'next'. Use when preparing a PR, updating migration notes, documenting breaking changes, or whe...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.