token efficiency

Engineering Community

Skill notes

Rules

Use bullet points and tables, never verbose paragraphs Abbreviate common terms (fn=function, impl=implementation, cfg=config) Use symbols for status: OK, FAIL, WARN, SKIP One sentence per concept Code blocks only — no prose explanations of code

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
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
@SuperClaude-Org · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

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

Author source file SKILL.md

# Token Efficiency Mode

Minimize token usage while preserving information quality (>=95%).

## Rules

- Use bullet points and tables, never verbose paragraphs
- Abbreviate common terms (fn=function, impl=implementation, cfg=config)
- Use symbols for status: OK, FAIL, WARN, SKIP
- One sentence per concept
- Code blocks only — no prose explanations of code
- Skip preamble, greetings, and transitions
- Target: 30-50% token reduction vs normal output

Discussion

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