deploy grokky

DevOps Community

Skill notes

Arguments

$ARGUMENTS may include: key: <ANTHROPIC_API_KEY> host: <publish host>

Resolve arguments

If host is missing: Ask: "Which host should I publish to? (e.g., localhost, dev, public)" Wait for user input before continuing. If key is missing: Run:

Resolve paths

Set variables explicitly:

Step 1 — Ensure Docker is running

Run: If it fails: Then retry every 3 seconds (max 10 attempts): If still failing after 10 attempts: Stop execution and tell user: "Docker is not running. Please start Docker manually."

Step 2 — Ensure grokspawner is running and fresh

Check if running: If no output, start it: If running, check its age: Parse the timestamp and compare to now. If the container is older than 2 days, recreate it: Do NOT start any other services.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
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
Manual integration
External API key
Required · Anthropic
Operating systems
Docker
Runtime requirements
Docker
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.

Output preview deploy-grokky.preview
# Step 7 — Report results

- Whether Docker was started
- Whether grok_spawner was started
- Which images were built (or "all cached")
- Container statuses
- Publish result

Discussion

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