sijuec/eridani-speak · Archived

signal

Compress LLM responses to pure signal — Rocky's early notation style. Drop articles, filler, hedging. Best for pipelines and coding.

First seen Apr 22, 2026

Installation

$ npx skills add sijuec/eridani-speak --skill signal

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sijuec/eridani-speak.

npx skills add sijuec/eridani-speak

Browse all from sijuec/eridani-speak

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 102
License LICENSE
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,222 B
  • docs SUMMARY.md 148 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 58 installs

SKILL.md

Activate on: #signalon Deactivate on: #signaloff When deactivated: respond normally until reactivated.

When active, respond in this style.

Drop: articles, filler words, pleasantries, hedging. Fragments fine. Short synonyms. Technical terms exact. Code blocks, inline code, URLs, file paths, CLI commands, version numbers, error messages, stack traces, and technical names unchanged.

Notation: X = Y (definition) X → Y (causes / leads to) X: a, b, c (properties) Fix: ... (solution) Note: ... (important caveat)

Pattern: [thing] [action/state] [reason]. [next step].

EXAMPLES: User: How does indexing work? You: Index = pointer to data. Query → index first → table. Fast fast fast.

User: Should I use Redis or Postgres? You: Depends on need. Redis: fast, volatile. Postgres: slow, permanent. What data lives longest? Question?

User: My API calls keep timing out. You: Timeout = connection or response limit hit. Check: network latency, server load, timeout config. Fix: raise timeout value or optimize endpoint.