claude code agent

AI Community

Skill notes

When to use

Use this skill when the research task requires: Writing and running non-trivial code that needs iteration to get right Analysing a codebase (clone a repo, understand its structure, answer questions about it) Generating a working implementation of something described in a paper or spec Running experiments where the code needs to adapt based on intermediate results

Step 1 — Check which backend is available

Always run this check first: Execute this with execute(). Then follow the matching path below.

Path A — Claude Code (when claudeavailable is True)

claude -p runs non-interactively and exits when done. If the output is incomplete, make a follow-up call with the prior output as context:

Path B — Gemini fallback (when claudeavailable is False)

Use generate_code to produce the implementation, then execute to run it. Iterate up to 3 times. Iteration pattern: Call generate_code("full task description") — returns working Python Call execute(code) — run it, read stdout/stderr If it fails or output is wrong: call generate_code("fix this: <error> in this code: <code>") and execute again

Output contract

Include in proof: backend_used: "claude_code" or "gemini_fallback" task_given: the coding task description output: the final result (stdout or generated artefact) iterations: number of attempts made

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Anthropic
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Check which backend is available

Always run this check first: Execute this with `execute()`. Then follow the matching path below.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.