skills/challenge/SKILL.md
--- tldr: Constructive pushback on a proposal — surface blind spots, alternatives, and risks without being adversarial category: planning --- # /eidos:challenge Push back constructively on a proposal. Not adversarial — just honest feedback on what you might not have considered. ## Usage ``` /eidos:challenge [proposal or idea] ``` ## Instructions 1. Read the proposal carefully — understand what's being proposed and why 2. Assume the idea has merit — start from "this could work" not "this is
npx skillsauth add agenticnotetaking/eidos skills/challengeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Push back constructively on a proposal. Not adversarial — just honest feedback on what you might not have considered.
/eidos:challenge [proposal or idea]
Read the proposal carefully — understand what's being proposed and why
Assume the idea has merit — start from "this could work" not "this is wrong"
Surface feedback in these categories (skip any that don't apply):
Blind spots — things the proposal doesn't address that it probably should Alternatives — other approaches that might achieve the same goal, with trade-offs Risks — what could go wrong or become painful later Simplification — is there a simpler version that captures 80% of the value? Tension — does this conflict with existing specs, patterns, or decisions?
For each point, explain why it matters — don't just list objections
End with an honest overall take: is this a good idea, a good idea that needs refinement, or worth reconsidering?
Structured feedback under the applicable category headings. Closes with an overall assessment and suggested next step.
tools
--- tldr: Generate a manim explainer video through staged research → outline → scenes → code → render → merge, with the outline doubling as a plan/state document category: utility --- # /eidos:video Turn a topic (or a folder of wiki-linked md) into a rendered manim video through a fixed pipeline. Pauses after each stage for review by default. Outline doubles as the plan/state document — wiki-linked checklist tracks progress. Full design in [[spec - video skill - outline driven manim pipeline
tools
--- tldr: Surface session status to the human via a native OS notification category: utility --- # /eidos:ping Send a short out-of-band signal to the human — "I'm done", "I have a question", "I hit a wall" — as a native OS notification. The agent picks the moment; the human gets a popup without watching the terminal. ## Setup (macOS, opt-in) This skill is a no-op until the human has installed the **eidos-ping** menubar app and pointed at it in `.eidos-config.yaml`: ```yaml ping_macos: /path
tools
--- tldr: Persist behaviour corrections to CLAUDE.md category: utility --- # /eidos:toclaude Update CLAUDE.md or specs to correct undesired behaviour. ## Usage ``` /eidos:toclaude [description of correction] ``` ## Instructions 1. Understand the correction — what went wrong, what should happen instead 2. Identify the right location: - **`inject/core/*.md`** — plugin rules that apply to all eidos projects (pick the matching section file) - **`inject/feature/*.md`** — rules tied to a c
development
--- tldr: Create persistent plan for multi-step work category: planning --- # /eidos:plan Create a persistent plan file for multi-step work. ## Usage ``` /eidos:plan [brief description] ``` ## Instructions ### 1. Gather Context If the target file already exists with `status: seed`, read it — its content is raw context that seeds the plan. Use the seed's notes, links, and brain dumps to draft phases and actions. Skip clarification questions the seed already covers. Search for related arti