pikoCNC G-CODE

v1.0.0

Interprets and executes full PikoCNC G-code commands with modal state tracking, motion control, parameter handling, and error detection for CNC machining.

0· 52·0 current·0 all-time
byKamil Szymoniak@midware
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (PikoCNC G-code interpreter/executor) match the content of SKILL.md: a complete specification and implementation notes for a G-code interpreter. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
SKILL.md is a detailed, implementation-oriented guide for parsing, modal-state tracking, and executing G-code. It does not instruct the agent to read unrelated files, access environment variables, or call external endpoints. Note: the document is focused on building an interpreter/simulator; it does not provide or require instructions for safely interfacing with physical CNC hardware (emergency stops, hardware interlocks, permissions), so implementing or running produced code on real machines carries physical-safety risk that the spec does not fully mitigate.
Install Mechanism
There is no install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk by the skill package itself.
Credentials
The skill declares no environment variables, no credentials, and no config paths. That is proportionate for an instruction/specification-only skill.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent system presence or elevated privileges. Autonomous invocation is allowed by default but is not combined with other concerning capabilities here.
Assessment
This skill is a coherent, text-only specification for implementing a G-code interpreter — it won't access your system or cloud keys by itself. Before using any interpreter you build from this: test extensively in simulator/dry-run mode; validate and sanitize all G-code inputs; implement hardware safety features (limit switches, feed overrides, emergency stop) before connecting to a real machine; and prefer running on isolated test equipment first. Also note the package source/homepage is unknown — if you plan to rely on this in production, get provenance or a reviewed implementation from a trusted source.

Like a lobster shell, security has layers — review code before you run it.

latestvk97frzafea4g2ffzxmcg98bkds83r027

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments