Sanexxxx777
- 11 skills
- 0 followers
- 1 day ago last updated
- ▌ Evidence To Skill · sanexxxx777 bundleConvert repositories, books, incident reports, transcripts, documentation, and other source material into the smallest justified AI skill or reference artifact. Use when extracting reusable practices from external or internal sources, deciding whether material deserves promotion into agent instructions, building an evidence ledger, preserving attribution, or auditing a generated skill for unsafe authority, secret-shaped content, and unjustified claims.
- ▌ Vet · sanexxxx777Evaluate an incoming workflow upgrade — a skill, MCP server, subagent, library, external service, prompt, or pattern — through one disciplined pipeline before adopting it. Security is a blocking gate. Records every verdict so the same thing is never evaluated twice. Use when considering a new tool from a post, repo, or recommendation. Triggers — "vet this", "should we adopt", "is this safe to install", "evaluate this skill/MCP", "what do you think of this tool".
- ▌ Goal · sanexxxx777Autonomous goal loop — give it ONE goal plus how to verify it, the agent runs check→fix→check itself and comes back only with the finished result (code with audit, research with fact-check, content with critique, audit/backtest). Self-verification instead of constant supervision, with hard safety guards. Vary the loop with a verification rubric designed before it runs. Triggers — "work autonomously to the result", "don't come back until it's done", "run the loop yourself", "drive it to done".
- ▌
- ▌ Teach · sanexxxx777Teacher mode — turn a session recap / article / docs / concept / piece of code / bug into an incremental mini-course with comprehension checks, quizzes, and an auto-saved summary note. Invoke /teach [topic or URL]. Triggers — "explain it like a teacher", "walk me through what we did", "turn this into a lesson", "quiz me", "teach me", "let's learn this together".
- ▌ Longread · sanexxxx777Write an analytical longform piece — a 4-phase pipeline from raw idea to finished text, with research-backed facts and a devil's-advocate pass before publishing. Invoke /longread <topic>. Triggers — "write a longread about X", "write an analytical breakdown of Y", "write an expert post", "turn this into an article".
- ▌
- ▌ Konsilium · sanexxxx777Council — 5 independent AI perspectives + mutual critique + synthesis (adapted from karpathy/llm-council for Claude Code). For high-stakes decisions where the answer does NOT follow unambiguously from the data — go/no-go before real consequences, critiquing a methodology, choosing between competing approaches, pressure-testing a conclusion you're attached to, designing risk controls. NOT for log/data analysis (the council has no data access) and not for factual lookups. Triggers — "convene the council", "run it past the council", "go/no-go", "pressure-test this".
- ▌
- ▌ System Health · sanexxxx777Preventive hygiene audit of your own Claude Code configuration — memory files, project context (CLAUDE.md), rules, permissions, skills — a deterministic scan of sizes / broken links / stale entries / excessive permissions / junk + interpretation + targeted fixes by agreement. Keeps the setup from rotting before it breaks. Triggers — "check the system", "system health", "workflow hygiene", "what to clean up", "audit memory", "optimize the system".
- ▌ Workflow Upgrade · sanexxxx777Deliberate system-improvement loop — audit your own Claude Code setup (rules / memory / skills / MCP / agents / registry), evaluate incoming tools via /vet, adopt the worthwhile ones with discipline (backup → verify), and record every decision. Use when bringing in a tool/idea/collection to improve the setup, or when doing a tooling-improvement pass. Triggers — "upgrade the workflow", "audit our setup", "let's improve the tooling", "evaluate this for us", when handed a post/repo/reel with a tool.