All authors
Claude Skills by grahama1970
github.com/grahama1970316 skills1 installs496 views
- Best Practices Github TicketBest practices for agent-resolved GitHub tickets, including bugs, feature requests, optimizations, maintenance, questions, and triage: filing contracts, route and subagent metadata, resolver leases, deterministic verification, review evidence, WebGPT escalation, and proof-based closure.Votes: 0GitHub stars: 6
- Best Practices GreenfieldUse for greenfield collaboration where the final product, architecture, workflow, schema, prompt, memory representation, visual direction, evaluation method, or implementation path is not fully known. Forces one named artifact, one visible contract, one candidate, one inspection, one status, and one next legal move instead of issue-tracker drift or broad architecture theater.Votes: 0GitHub stars: 6
- Best Practices KdeRepo-specific KDE/QML best practices for agentic coding: singleton design systems, property ordering, accessibility, performance (binding loops, delegate recycling), Plasma integration, and D-Bus patterns.Votes: 0GitHub stars: 6
- Best Practices Kling Contact SheetCreate, audit, and package AI-video-ready reference packs for Kling-style element binding. Use when users ask for Kling contact sheets, Kling-ready assets, element reference packs, character reference sheets, prop sheets, scene sheets, or consistent AI-video references.Votes: 0GitHub stars: 6
- Best Practices Kling VideoBest practices for generating faithful Kling videos via fal.ai: endpoint selection (reference-to-video vs image-to-video vs text-to-video), character identity locking with elements, prompt condensation from large pipeline artifacts (storyboards, character bibles, look locks) into Kling-sized prompts, and typed request validation. Use when Kling output does not match contact sheets or reference images, when characters render as wrong people, when choosing a Kling endpoint, when compiling a per...Votes: 0GitHub stars: 6
- Best Practices One ShotBest practices for Ask one-shot runs: the same question to N seats concurrently, answers returned per seat with no consensus, no judge, and no quorum. Use when a user asks several models one question and wants to read each answer, when partial answers are still useful, or when deciding whether a request is a one-shot, a roundtable, or a competition.Votes: 0GitHub stars: 6
- Best Practices OpportunitiesCanonical rubric for evaluating, scoring, ranking, and gating career and consulting opportunities for Graham Anderson, so the "top opportunities" selection is principled and repeatable rather than bespoke per run. Use when discovering, evaluating, reviewing, ranking, or deciding which opportunities to apply to in monitor-opportunities, or when building or reviewing the opportunity-evaluator / opportunity-evaluation-reviewer subagents or the ranker. The evaluator scores AGAINST this rubric; th...Votes: 0GitHub stars: 6
- Best Practices Pi ExtensionBest practices for building, reviewing, and shipping Pi TypeScript extensions and extension packages. Use when authoring Pi extensions, custom tools, lifecycle hooks, intercom bridges, status guards, provider adapters, TUI components, package manifests, or retained extension evals.Votes: 0GitHub stars: 6
- Best Practices Pi ExtensionsEvidence-backed standards for creating, reviewing, and hardening Pi extensions. Use when building or changing ~/.pi/agent/extensions or .pi/extensions code, package-style Pi extensions, event handlers, custom tools, TypeBox schemas, input/message/tool hooks, retry guards, final-report guards, or humorous but serious enforcement extensions such as lazy-report-shame-shame-shame.Votes: 0GitHub stars: 6
- Best Practices PitchdeckDeck ARCHITECTURE rules for building pitch decks from source material — measured from a real 263-slide corpus, not invented. Use when planning a deck's sections and slide sequence, when deciding which source images become slides, or when reviewing whether a generated deck is house-shaped. Exists to prevent bespoking slide architecture: sections must be DERIVED from the source document, never hardcoded in a compiler.Votes: 0GitHub stars: 6
- Best Practices PlanBest practices for orchestration-ready task files. Enforces adversarial testing, skill chain syntax, definition-of-done requirements, gate definitions, persona routing, and /model directives. Referenced by /plan and /review-plan.Votes: 0GitHub stars: 6
- Best Practices PortBest practices for porting features from one codebase, app, harness, TUI, API, or workflow into another without losing destination-specific behavior. Use when users ask to port, clone, migrate, replicate parity, achieve functional equivalence, borrow features, compare source vs destination, or preserve custom work while importing behavior from a reference implementation.Votes: 0GitHub stars: 6
- Best Practices Project StateStandards and workflow for creating root-level PROJECT_STATE.md reports from local receipts, project knowledge, stale/aspirational audits, competitor research, and external reviewer evidence. Use when asked for project state, comprehensive project review, "what works and what is missing", stale code/doc assessment, competitive positioning, or a PROJECT_STATE.md deliverable.Votes: 0GitHub stars: 6
- Best Practices ProjectProject-readiness policy for skills-first repositories and substantial skills. Use when creating, auditing, or declaring a project ready; when deciding which best-practices-* packs apply; when a repo needs setup-project provenance, PROJECT_KNOWLEDGE, explain-project records, cleanup evidence, or retained agentic evals, acceptance-contract gates, Battle evidence, and release reports before it can be called developer-ready.Votes: 0GitHub stars: 6
- Best Practices PromptRules for writing clear, testable LLM prompts. Eliminates vagueness, enforces concrete output specs, grounding in source material, and deterministic verifiability. Gate before /review-prompt.Votes: 0GitHub stars: 6
- Best Practices PythonRepo-specific Python best practices for agentic coding: Loguru + Typer + uv + pyproject.toml, httpx over requests, functions-first, module docstrings, max 800 LOC per file, and non-mocked sanity tests.Votes: 0GitHub stars: 6
- Best Practices ReactReact, Next.js, React Native, and web design best practices from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js/React Native components, optimizing performance, auditing UI accessibility, or designing component APIs. Triggers: "review react", "optimize component", "check accessibility", "react best practices", "component architecture", "react native performance".Votes: 0GitHub stars: 6
- Vercel Deploy ClaimableDeploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.Votes: 0GitHub stars: 6
- Composition PatternsComposition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. These patterns make codebases easier for both humans and AI agents to work with as they scale.Votes: 0GitHub stars: 6
- React Best PracticesReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.Votes: 0GitHub stars: 6
- React Native SkillsComprehensive best practices for React Native and Expo applications. Contains rules across multiple categories covering performance, animations, UI patterns, and platform-specific optimizations.Votes: 0GitHub stars: 6
- Best Practices ReadmeStandards and templates for writing concise, welcoming, evidence-aware README.md files for agent-skills skills, public project pages, gallery card destinations, architectural playground repos, and developer-facing docs. Use when creating or reviewing README prose, README structure, project/skill landing pages, image-card destinations, public/private runtime notices, proof and non-claim sections, or documentation meant to be browsed by developers.Votes: 0GitHub stars: 6
- Best Practices ReportProduce evidence-bearing technical reports and report UIs without dashboard theater. Use when creating or reviewing reports, HTML/CSS report surfaces, implementation reviews, design reviews, application inventories, validation readouts, evidence ledgers, status/readiness reports, compliance/control summaries, source-of-truth audits, or issue-to-plan repair reports that must expose persona, primary object, source of truth, findings, rationale, blockers, valid actions, acceptance checks, non-cl...Votes: 0GitHub stars: 6
- Best Practices ResumeCanonical rules for writing, formatting, exporting, and verifying Graham Anderson's resume and its public surfaces, so an agent never re-derives them by trial and error. Use when editing RESUME.md, changing the resume PDF, DOCX, Markdown or /resume page, reconciling LinkedIn with the resume, deciding page count or section order, judging whether a claim may be made, or verifying a built resume artifact. /resume executes; this skill decides.Votes: 0GitHub stars: 6
- Best Practices RoundtableBest practices for leading multi-model Ask roundtables and Tau-DAG deliberation panels. Use when a user asks for a roundtable, model panel, mixed web/API collaborator discussion, multi-round critique, attributed dissent synthesis, or guidance on turning several model perspectives into executable next steps through $ask.Votes: 0GitHub stars: 6
- Best Practices RustRepo-specific Rust best practices for agentic coding: thiserror + anyhow error handling, tokio async runtime, tracing for observability, clap for CLI, axum for HTTP, serde patterns, cargo workspace conventions, ownership and lifetimes, and idiomatic Rust 2024 edition patterns.Votes: 0GitHub stars: 6
- Best Practices Scene Script WritingWriting standard for scene scripts and beat descriptions that feed AI video generation: how to describe environment, weather, lighting, and every character/prop interaction with concrete physical states and motion verbs so the persona-dream panel gate passes and rendered clips have life instead of static tableaus. Use when writing or reviewing a scene script, storyboard panel text, dream story beat, or provider prompt whose elements lack physical state, environmental interaction, weather, or ...Votes: 0GitHub stars: 6
- Best Practices ScillmError recovery and anti-patterns for scillm LLM proxy. Load this when scillm calls fail, timeout, or return unexpected results. Covers batch sizing, header requirements, model selection, and debugging workflow.Votes: 0GitHub stars: 6
- Best Practices SecurityGeneral application, service, plugin, and agent security hardening baseline. Use before /hack, /security-scan, /code-runner probe generation, or security review. Grounded in OWASP ASVS, OWASP Cheat Sheet Series, Node.js security guidance, and agent/plugin trust-boundary lessons.Votes: 0GitHub stars: 6
- Best Practices Self Improvement LoopDeterministic coded self-improvement loops for *-lab skills. The agent will NOT do this reliably — loops MUST be in code. Proven pattern from Classifier Lab: data_enrichment.py + training_loop.py.Votes: 0GitHub stars: 6
- Best Practices SkillsBest practices for designing and structuring agent skills: SKILL.md frontmatter rules, triggers, progressive disclosure, and when to use scripts vs references.Votes: 0GitHub stars: 6
- Best Practices Slide DesignSlide design craft for /pitchdeck: assertion headlines, distance-legible chrome, multi-channel reinforcement, density limits, audience-parameterized arcs, responsive browser presentation, and house theme templates. Use when planning, drafting, critiquing, or restyling a deck; when slides look like "blue boxes"; when choosing layouts, fonts, or themes; or when converting a reference PPTX into a house style.Votes: 0GitHub stars: 6
- Best Practices SpartaBest practices for the SPARTA pipeline: data model, edge persistence, QRA generation, ArangoDB collections, and common gotchas learned the hard way.Votes: 0GitHub stars: 6
- Best Practices StreamdeckProject-specific best practices for the Stream Deck control suite: icon format constraints, socket vs config boundaries, widget button lifecycle, page creation via build_page, ArangoDB fallback patterns, and NVIS palette compliance.Votes: 0GitHub stars: 6
- Best Practices SubagentCanonical contract, tool-policy vocabulary, memory/ToM-lite rules, helper delegation, receipt requirements, and retry budgets for Scillm/OpenCode/$loop subagents and persona workers.Votes: 0GitHub stars: 6
- Best Practices Tau DagBest practices for authoring, reviewing, and repairing Tau DAG contracts. Use when creating tau.dag_contract.v1 YAML/JSON, choosing project-agent subagent roles, declaring immutable goals, adding skill gates such as best-practices-prompt/react/python, specifying provider/model policy, or diagnosing project-agent DAG failures and tau.dag_error.v1 course-corrections.Votes: 0GitHub stars: 6
- BootcampGuided onboarding walkthrough for new Embry OS users via Embry Lawson personaVotes: 0GitHub stars: 6
- Brave SearchFree web, local, LLM Context, and optional Summarizer search via Brave Search API. Use when user says "brave search", "search with brave", "brave web search", "brave local search", "local search", "find businesses near", "near me", "Brave LLM context", or "Brave summarizer".Votes: 0GitHub stars: 6
- Browser OraclePersistent browser-oracle tab bindings and directory walk-up registry for WebGPT, Cursor Browser, Gemini, Kimi, and Claude. Binds tab id / viewId + URL once under ~/.pi; maps directories to project names via .ask/browser-oracles.yaml discovered like python-dotenv parent walk-up.Votes: 0GitHub stars: 6
- CaptchaAuthorization-gated CAPTCHA security evaluation using the pinned ReCAP agent, synthetic dynamic CAPTCHA challenges on loopback, Surf transport proof, and Ask DAG composition. Use when the user says "evaluate CAPTCHA security", "benchmark ReCAP", "test a local CAPTCHA agent", or "measure CAPTCHA robustness".Votes: 0GitHub stars: 6
- Casting AgentResearch and decide visual casting for persona-dream/movie entities before contact-sheet generation. Use when a story, screenplay, storyboard, or visual_entities.json needs characters, creatures, props, environments, moods, time periods, states, or user-provided reference images turned into a casting_contract.json for downstream contact sheets. Use for "casting agent", "visual casting", "choose references", "research character look", "use these image paths as references", "Brave-search for re...Votes: 0GitHub stars: 6
- CcopyCopy the last complete Cursor user/assistant turn to the clipboard (Codex-style /copy). On modern Cursor Agent installs reads ~/.cursor/projects/*/agent-transcripts/*.jsonl when SQLite bubbleId rows are absent. Use for ccopy, cursor copy, or export last Cursor turn.Votes: 0GitHub stars: 6
- Chatterbox SpeakThin front door for speaking a line through the live Chatterbox service with a named voice, tone, context note, and emotional intensity. Use when a project agent says "speak", "say this out loud", "speak as embry", "chatterbox speak", "render this with a sigh", or wants one-shot voiced output with a receipt without the full embry-voice-control turn pipeline.Votes: 0GitHub stars: 6
- CheckpointSession grading and cataloging for the learning flywheel. Stores checkpoints in ArangoDB via httpx to memory daemon — findable by BM25, semantic search, and multi-hop graph traversal. Grades sessions with a 5-level rubric, stores proven/failed skill chains for /recommend-skill-chain, links to episodic archives, and cross-references ~/.claude/ memory. Git commits both project AND skills on every save. NON-NEGOTIABLE.Votes: 0GitHub stars: 6
- Chutes CallCentralized Chutes.ai LLM gateway as a shared Docker service. Global 5-slot semaphore enforces account concurrency limit across all agents. Single and batch calls with tenacious retry mode, circuit breaker, fallback chain, NDJSON streaming, and structured request/response objects with JSON cleaning.Votes: 0GitHub stars: 6
- Classifier Lab SubagentValidate subagent reliability by running 3 concurrent classifier training loops. Each subagent runs /classifier-lab (deterministic code) and reports via JSON stream. The subagent's only job: run the skill, fix crashes, write /test-lab tests. 90% code, 10% agent. HP adjustment between rounds uses /scillm Gemini structured JSON, not agent judgment.Votes: 0GitHub stars: 6
- Classifier LabMulti-modality classifier training lab. Train, evaluate, and deploy vision, text, and tabular classifiers using state-of-the-art backbones.Votes: 0GitHub stars: 6
- Clean TextNormalize text to handle PDF/Unicode encoding issues and security evasion. Converts Windows-1252, curly quotes, em/en dashes, ligatures, directional formatting, zero-width chars, and more to clean ASCII. Security extensions: homoglyph translation, mixed-script detection, invisible content detection, URL double-decoding, letter-spacing collapse.Votes: 0GitHub stars: 6
- CleanupAssess the project to reorganize or deprecate unused/outdated files. Joins each candidate against per-candidate dependency evidence, blocks mutation per class on the evidence that class actually needs, and keeps assessment running when indexing is unavailable.Votes: 0GitHub stars: 6
- Clipboard FileCopy files, zips, images, screenshots, artifacts, or bundles to the desktop clipboard as file-manager paste items. Use when the user says copy a file to clipboard, copy a zip to clipboard, copy an image to clipboard, put this artifact on the clipboard, or when KDE/X11, GNOME, xclip, text/uri-list, or x-special/gnome-copied-files clipboard targets matter.Votes: 0GitHub stars: 6