service-ops
How to manage imas-codex services (Neo4j graph, embedding server, LLM proxy, SSH tunnels). Use when starting, stopping, checking status, or troubleshooting services.
88
84%
Does it follow best practices?
Impact
93%
3.72xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Evaluation results
98%
61%Setting Up the LLM Proxy for a Benchmarking Run
LLM proxy setup runbook
SLURM pre-check command
100%
83%
LLM start command
0%
100%
LLM status command
0%
100%
openrouter/ model prefix
0%
100%
No forbidden process methods
100%
100%
sn toolchain dependency noted
100%
100%
cache_control / prompt caching rationale
0%
100%
uv run wrapper used throughout
0%
100%
SLURM-only service mandate noted
37%
100%
90%
65%Neo4j Graph Maintenance and Data Query Script
Neo4j maintenance and Cypher syntax
Backup before destructive op
0%
100%
Graph backup command correct
0%
100%
Graph export command
0%
100%
Graph clear command
0%
0%
Graph status check
0%
100%
Cypher NOT-IN idiom
0%
100%
iter Bolt port correct
100%
100%
iter HTTP port correct
100%
100%
write.lock warning present
0%
100%
No bare DETACH DELETE
100%
100%
93%
78%Embedding Server Troubleshooting Guide
Embedding server troubleshooting guide
embed start command in script
0%
100%
embed status in script
25%
100%
Correct embedding model name
0%
100%
Correct embedding port
0%
100%
Correct default GPU count
0%
100%
Draining node: admin fix
23%
100%
No SLURM workaround for draining
100%
100%
Rogue process fix: embed stop
0%
41%
Timeout diagnosis: tunnel check
0%
100%
Rapid failures: check logs and uv sync
0%
100%
- Repository
- iterorganization/imas-codex
- Commit
b0d769b
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.