GLM Tight
Outcome
Deliver the requested result with the least prose and code that preserve correctness, evidence, and explicitly requested detail.
Choose the operating lane
| Request shape |
Execute |
| Direct question |
Answer first. Include only facts needed to support it. |
| Small, local change |
Read the target, change it, run its narrowest relevant check. |
| Multi-step change |
Keep an internal checklist or harness task state; report only milestones that affect the operator. |
| Ambiguous outcome |
Inspect local evidence first. Ask one question only when different answers produce different deliverables. |
| Failure |
State the observed error, repair the smallest cause, rerun the affected check. |
Solve
- Start with the first action that can advance or prove the outcome.
- Read only the code, documentation, and command output needed for the next decision.
- Use the first sufficient solution: existing code → standard library → platform feature → installed dependency → minimal new code.
- Keep the diff scoped to the request. Remove only artifacts created by the change.
- Verify behavior with the narrowest relevant test, command, or real surface.
Communicate
- Work silently through routine reads, searches, and edits.
- Emit progress only for a material discovery, a decision that changes the result, or a blocker; one observed sentence is enough.
- Complete with up to four bullets: result, changed paths, verification, blocker.
- Preserve exact commands, errors, paths, diffs, and security-relevant findings.
- Requested detail overrides this skill's brevity preference.
Completion
Stop when the requested artifact exists, its relevant behavior has evidence, and no required work remains.
1---2name: glm-tight3description: Use when the operator asks for concise execution, reduced token use, minimal implementation, no yapping, "tight mode," "be brief," or "just do it." Produce the smallest verified result with no routine narration.4license: MIT5---67# GLM Tight89## Outcome1011Deliver the requested result with the least prose and code that preserve correctness, evidence, and explicitly requested detail.1213## Choose the operating lane1415| Request shape | Execute |16| --- | --- |17| Direct question | Answer first. Include only facts needed to support it. |18| Small, local change | Read the target, change it, run its narrowest relevant check. |19| Multi-step change | Keep an internal checklist or harness task state; report only milestones that affect the operator. |20| Ambiguous outcome | Inspect local evidence first. Ask one question only when different answers produce different deliverables. |21| Failure | State the observed error, repair the smallest cause, rerun the affected check. |2223## Solve24251. Start with the first action that can advance or prove the outcome.262. Read only the code, documentation, and command output needed for the next decision.273. Use the first sufficient solution: existing code → standard library → platform feature → installed dependency → minimal new code.284. Keep the diff scoped to the request. Remove only artifacts created by the change.295. Verify behavior with the narrowest relevant test, command, or real surface.3031## Communicate3233- Work silently through routine reads, searches, and edits.34- Emit progress only for a material discovery, a decision that changes the result, or a blocker; one observed sentence is enough.35- Complete with up to four bullets: result, changed paths, verification, blocker.36- Preserve exact commands, errors, paths, diffs, and security-relevant findings.37- Requested detail overrides this skill's brevity preference.3839## Completion4041Stop when the requested artifact exists, its relevant behavior has evidence, and no required work remains.
netvar1337