Ark Analysis
Skill438 starsChanged 7 months agoApache-2.0View on GitHub
Analyze the Ark codebase by cloning the repository to a temporary location. Use this skill when the user asks questions about how Ark works, wants to understand Ark's implementation, or needs to examine Ark source code.
- Deletes or force-pushes
In this repository29 other files it gives its agents.
- ark/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- a2a-protocolSkill
- ark-architectureSkill
- ark-controller-developmentSkill
- ark-dependabot-managementSkill
- ark-sdk-developmentSkill
- ark-setup-clusterSkill
- ark-chainsaw-testingSkill
- Ark Dashboard and UI TestingSkill
- ark-documentationSkill
- issue-creationSkill
- ark-issuesSkill
- multi-branch-cluster-setupSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- ark-pentest-issue-resolverSkill
- ark-researchSkill
- slack-announcementSkill
- ark-vulnerability-fixerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when:
- Very specific: line 77
Clone to /tmp: Always clone to /tmp/ark-analysis to avoid cluttering the workspace
- Very specific: line 79
Use search tools: Prefer rg (ripgrep) or grep for code searches
- Distinctive: line 80
Check CLAUDE.md: Look for project-specific guidance in CLAUDE.md files
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Ark Analysis
This skill helps you analyze the Ark codebase by cloning the repository and examining its contents.
When to use this skill
Use this skill when:
- User asks "how does X work in Ark?"
- User wants to understand Ark's architecture or implementation
- User needs to examine Ark source code, CRDs, or controllers
- User mentions analyzing the Ark repository
Quick start
Clone the Ark repository to a temporary location:
git clone git@github.com:mckinsey/agents-at-scale-ark.git /tmp/ark-analysis
cd /tmp/ark-analysisCodebase structure
The Ark repository is organized as follows:
ark/- Kubernetes operator and default executor (Go)- Controller dispatches queries to executors via A2A protocol
- CRDs: Agent, Model, Query, Team, MCPServer, ExecutionEngine, A2AServer
executors/completions/- Built-in default execution engine
lib/ark-sdk/- Python SDK (generated + overlay)BaseExecutorABC andExecutorAppfor pluggable executor interface
services/- Component servicesark-api/- REST API gateway (Python/FastAPI)ark-broker/- In-memory event bus (Node.js/Express)ark-dashboard/- Web UI (Next.js/React)
samples/- Example YAML configurationsdocs/- Documentation site (Next.js/MDX)
Common analysis tasks
Find controllers
ls ark/internal/controller/
grep -r "Reconcile" ark/internal/controller/Find CRDs
ls ark/config/crd/bases/
grep -r "kind: Agent" samples/Find A2A implementations
find . -path "*/a2a*" -type f
grep -r "A2AServer" .Search for specific features
# Use ripgrep or grep to search
rg "query controller" --type go
grep -r "team coordination" --include="*.go"Best practices
- Clone to /tmp: Always clone to
/tmp/ark-analysisto avoid cluttering the workspace - Navigate first:
cd /tmp/ark-analysisbefore running analysis commands - Use search tools: Prefer
rg(ripgrep) orgrepfor code searches - Check CLAUDE.md: Look for project-specific guidance in
CLAUDE.mdfiles - Clean up: Optionally remove the temp directory when done:
rm -rf /tmp/ark-analysis
Example workflows
Analyzing a controller
git clone git@github.com:mckinsey/agents-at-scale-ark.git /tmp/ark-analysis
cd /tmp/ark-analysis
cat ark/internal/controller/query_controller.go
grep -r "ExecuteQuery" ark/internal/genai/Understanding A2A integration
cd /tmp/ark-analysis
find samples/a2a -name "*.py"
cat samples/a2a/simple-agent/src/simple_a2a_server/main.py
cat docs/content/developer-guide/building-a2a-servers.mdxFinding CRD specifications
cd /tmp/ark-analysis
ls ark/api/v1alpha1/
cat ark/api/v1alpha1/agent_types.goDoes 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
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.

