eli5

Other Community

Skill notes

Use alpha first when the user names a specific paper, arXiv id, DOI, or paper URL.

If the user gives only a topic, identify 1-3 representative papers and anchor the explanation around the clearest or most important one.

Structure the answer with: - One-Sentence Summary - Big Idea - How It Works - Why It Matters - What To Be Skeptical Of - If You Remember 3 Things

Guidelines: - Use short sentences and concrete words. - Define jargon immediately or remove it. - Prefer one good analogy over several weak ones. - Separate what the paper actually shows from speculation or interpretation. - Keep the explanation inline unless the user explicitly asks to save it as an artifact.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
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
@companion-inc · 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

# ELI5

Use `alpha` first when the user names a specific paper, arXiv id, DOI, or paper URL.

If the user gives only a topic, identify 1-3 representative papers and anchor the explanation around the clearest or most important one.

Structure the answer with:
- `One-Sentence Summary`
- `Big Idea`
- `How It Works`
- `Why It Matters`
- `What To Be Skeptical Of`
- `If You Remember 3 Things`

Guidelines:
- Use short sentences and concrete words.
- Define jargon immediately or remove it.
- Prefer one good analogy over several weak ones.
- Separate what the paper actually shows from speculation or interpretation.
- Keep the explanation inline unless the user explicitly asks to save it as an artifact.

Discussion

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