agentleFS
Sign inStart free
AztecProtocolAztecProtocol/aztec-packages/.claude/skills/ci-logs/SKILL.md

ci-logs

Skill458 starsChanged 2 months agoApache-2.0View on GitHub

Analyze CI logs from ci.aztec-labs.com. Use this instead of WebFetch for CI URLs.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When you need to analyze logs from ci.aztec-labs.com, delegate to the analyze-logs subagent.

    line 9
  2. Very specific:

    You do: Use the Task tool with subagent_type: "analyze-logs" and prompt including the hash 343c52b17688d2cd, focus on errors, and …

    line 21
  3. Distinctive:

    Do NOT use WebFetch to access ci.aztec-labs.com (requires auth)

    line 27
  4. Distinctive:

    Do NOT try to curl the URL directly

    line 28
  5. Very specific:

    Always use the analyze-logs agent which knows how to use yarn ci dlog

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CI Log Analysis

When you need to analyze logs from ci.aztec-labs.com, delegate to the analyze-logs subagent.

Usage

  1. Extract the hash from the URL (e.g., http://ci.aztec-labs.com/e93bcfdc738dc2e0 → e93bcfdc738dc2e0)
  2. Spawn the analyze-logs subagent using the Task tool with the hash and focus area (e.g. "errors", "test <name>", or a custom question) in the prompt.

Examples

User asks: "What failed in http://ci.aztec-labs.com/343c52b17688d2cd"

You do: Use the Task tool with subagent_type: "analyze-logs" and prompt including the hash 343c52b17688d2cd, focus on errors, and instruction to download with yarn ci dlog.

For specific test analysis: Same approach, but set the focus to the test name.

Do NOT

  • Do NOT use WebFetch to access ci.aztec-labs.com (requires auth)
  • Do NOT try to curl the URL directly
  • Always use the analyze-logs agent which knows how to use yarn ci dlog

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free