agentsclimarketplace

The catalog

608,119 rows, by stacks then stars

  • Svelte template directives

    spences10/skills/svelte-template-directives Skill

    no license16★ repo

    Svelte template directive guidance. Use when working with snippets, attachments, dynamic HTML, declaration tags, debugging tags, or global DOM events.

  • Sveltekit data flow

    spences10/skills/sveltekit-data-flow Skill

    no license16★ repo

    SvelteKit data flow guidance. Use when working with load functions, form actions, server/client boundaries, serialization, or invalidation.

  • Sveltekit remote functions

    spences10/skills/sveltekit-remote-functions Skill

    no license16★ repo

    Implement SvelteKit remote functions. Use for query(), query.live(), form(), command(), and prerender() patterns in .remote.ts files.

  • Sveltekit structure

    spences10/skills/sveltekit-structure Skill

    no license16★ repo

    SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.

  • Tdd

    spences10/skills/tdd Skill

    no license16★ repo

    Test-driven development with a red-green-refactor loop. Use when explicitly asked for TDD, red-green-refactor, test-first development, or integration-test-led feature work.

  • Techdebt finder

    spences10/skills/techdebt-finder Skill

    no license16★ repo

    Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.

  • Code review bar raising

    robisson/build-like-amazon-agent-skills/skills/code-review-bar-raising Skill

    16★ repo

    Applying Amazon's raise-the-bar principle to every code review. What reviewers look for — clarity, correctness, design, reuse, operational readiness. "Ship It" means the change raises or maintains the quality bar.

  • Correction of errors

    robisson/build-like-amazon-agent-skills/skills/correction-of-errors Skill

    16★ repo

    Blameless post-incident analysis focused on timeline, 5 Whys, mechanisms over people, and concrete action items with owners.

  • Dependency management

    robisson/build-like-amazon-agent-skills/skills/dependency-management Skill

    16★ repo

    Managing external dependencies safely with circuit breakers, timeouts, retries with exponential backoff, bulkhead pattern, graceful degradation, and dependency isolation.

  • Design document

    robisson/build-like-amazon-agent-skills/skills/design-document Skill

    16★ repo

    Writing a technical design document that translates a Working Backwards output into a concrete, reviewable engineering plan with architecture, trade-offs, cost estimation, and operational concerns.

  • Design review

    robisson/build-like-amazon-agent-skills/skills/design-review Skill

    16★ repo

    Review a technical design before specs or implementation. Evaluate problem clarity, requirements, alternatives, trade-offs, architecture, dependency behavior, security, operations, cost, testability, and simplicity.

  • Feature flag lifecycle

    robisson/build-like-amazon-agent-skills/skills/feature-flag-lifecycle Skill

    16★ repo

    Complete lifecycle of feature flags from creation through gradual rollout to cleanup, including kill switches and A/B testing.

  • Implementation memory

    robisson/build-like-amazon-agent-skills/skills/implementation-memory Skill

    16★ repo

    Internal /build flow mechanism that maintains fixed-size procedural memory of durable implementation-quality lessons.

  • Incremental implementation

    robisson/build-like-amazon-agent-skills/skills/incremental-implementation Skill

    16★ repo

    Implementing features in thin vertical slices that each deliver value independently. Feature flags, safe defaults, rollback-friendly changes. Never a big-bang deployment.

  • Infrastructure as code

    robisson/build-like-amazon-agent-skills/skills/infrastructure-as-code Skill

    16★ repo

    CDK/CloudFormation design principles for immutable infrastructure, environment parity, least privilege, tagging strategy, and cost optimization. Infrastructure is code—it deserves the same rigor as application code.

  • Mechanism creation

    robisson/build-like-amazon-agent-skills/skills/mechanism-creation Skill

    16★ repo

    Turning lessons learned into automated mechanisms that prevent recurrence of problems.

  • Metrics review

    robisson/build-like-amazon-agent-skills/skills/metrics-review Skill

    16★ repo

    Reviewing operational and business metrics for continuous improvement, trend analysis, and proactive issue detection.

  • Operational code

    robisson/build-like-amazon-agent-skills/skills/operational-code Skill

    16★ repo

    Writing code with built-in observability from day one. Structured logging (JSON), metrics emission (latency p50/p99, error rates), alarm-ready code, request tracing, graceful degradation.

  • Operational excellence

    robisson/build-like-amazon-agent-skills/skills/operational-excellence Skill

    16★ repo

    Dashboards, alarms, and runbooks that make a service operable. Covers latency, error rate, availability, throughput, and severity-based alarming.

  • Operational readiness review

    robisson/build-like-amazon-agent-skills/skills/operational-readiness-review Skill

    16★ repo

    The ORR process — a self-assessment checklist covering monitoring, alarming, runbooks, on-call, scaling, security, deployment safety, cost, and dependencies. Must pass before launch.

  • Pipeline safety

    robisson/build-like-amazon-agent-skills/skills/pipeline-safety Skill

    16★ repo

    CI/CD pipeline safety with automated gates, deployment blockers, alarm checks, and one-click rollback.

  • Progressive deployment

    robisson/build-like-amazon-agent-skills/skills/progressive-deployment Skill

    16★ repo

    Deploy changes incrementally through expanding blast radius stages with bake time and automatic rollback on alarm.

  • Spec driven implementation

    robisson/build-like-amazon-agent-skills/skills/spec-driven-implementation Skill

    16★ repo

    Bridge between an approved Design Document and code. Decompose the system-level blueprint into N vertical specs (requirements → design → tasks), each independently deliverable. Fail fast by ordering hardest-first. Execute wave-by-wave with approval gates.

  • Test driven development

    robisson/build-like-amazon-agent-skills/skills/test-driven-development Skill

    16★ repo

    Red-Green-Refactor cycle with Amazon's test pyramid (80% unit, 15% integration, 5% e2e). Coverage gates, DAMP over DRY in tests, canary tests in production.

  • Threat modeling

    robisson/build-like-amazon-agent-skills/skills/threat-modeling Skill

    16★ repo

    Security threat modeling using STRIDE methodology adapted for cloud services. Covers data classification, IAM boundaries, encryption requirements, blast radius analysis, and systematic identification of attack vectors before code is written.

  • Using amazon skills

    robisson/build-like-amazon-agent-skills/skills/using-amazon-skills Skill

    16★ repo

    Meta-skill for navigating and applying the complete skills library. Routing flow chart, core operating behaviors, and skill discovery logic.

  • Wb define

    robisson/build-like-amazon-agent-skills/skills/wb-define Skill

    16★ repo

    Stage 2 of Working Backwards: Articulate the customer's problem or opportunity with precision, using data to quantify impact and framing it in the customer's language — not engineering jargon.

  • Wb invent

    robisson/build-like-amazon-agent-skills/skills/wb-invent Skill

    16★ repo

    Stage 3 of Working Backwards: Generate multiple solution approaches, classify decisions as one-way vs two-way doors, evaluate alternatives against customer benefit and feasibility, and select the recommended solution with clear rationale.

  • Wb listen

    robisson/build-like-amazon-agent-skills/skills/wb-listen Skill

    16★ repo

    Stage 1 of Working Backwards: Identify who the customer is and gather deep insights about their current experience, pain points, and unmet needs through systematic observation and data collection.

  • Wb refine

    robisson/build-like-amazon-agent-skills/skills/wb-refine Skill

    16★ repo

    Stage 4 of Working Backwards: Write the PR/FAQ — a press release announcing the product as if it already exists, plus a comprehensive FAQ addressing hard questions. This is the core Amazon mechanism that forces clarity, customer-centric thinking, and rigorous pre-mortems before any code is written.

  • Wb test and iterate

    robisson/build-like-amazon-agent-skills/skills/wb-test-and-iterate Skill

    16★ repo

    Stage 5 of Working Backwards: Define how success will be measured using input and output metrics, set specific numeric targets, design experiments to validate assumptions, and plan iteration cycles based on data feedback.

  • Working backwards

    robisson/build-like-amazon-agent-skills/skills/working-backwards Skill

    16★ repo

    Entry point for developing new products, features, or initiatives using Amazon's Working Backwards process. Orchestrates 5 stages from customer insight to measurable success, starting with the 5 Customer Questions as a lightweight on-ramp before committing to a full PR/FAQ.

  • Commit

    kriscard/Skills/skills/dev/commit Skill

    16★ repo

    Creates semantic git commits with conventional commit format, stages selected changes safely, and optionally pushes to remote after explicit approval. Handles pre-commit hooks and writes meaningful commit messages. Use when the user says "commit", "push changes", "save to git", "commit this", or wants to create a git commit — even if they just say "save my work."

  • Debug

    kriscard/Skills/skills/dev/debug Skill

    16★ repo

    Debugs errors, test failures, and unexpected behavior with systematic root-cause analysis. Use when the user reports a bug, says "this isn't working", a test is failing, an exception is thrown, output is wrong, or asks to investigate "why does X happen". Applies to frontend, backend, database, network, and performance issues.

  • Frontend

    kriscard/Skills/skills/dev/frontend Skill

    16★ repo

    Frontend engineering audit for TypeScript, UI accessibility, Next.js boundaries, Tailwind/component patterns, and browser security. Use when reviewing .ts/.tsx/.jsx frontend code, designing UI components, checking type/runtime boundaries, handling XSS/CSP/token storage, or deciding frontend file structure. For React runtime/rendering pitfalls, use the react skill.

  • Pr review

    kriscard/Skills/skills/dev/pr-review Skill

    16★ repo

    Bug-first, evidence-only PR review with guidance-scoped specialist passes for security, correctness, architecture, React patterns, and accessibility. Use when the user says "review this PR", "review my changes", "review the diff", or mentions a PR number. Prefers silence over speculative findings.

  • React hook form audit

    kriscard/Skills/skills/dev/react-hook-form-audit Skill

    16★ repo

    Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.

  • React hook form

    kriscard/Skills/skills/dev/react-hook-form Skill

    16★ repo

    Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.

  • React

    kriscard/Skills/skills/dev/react Skill

    16★ repo

    Audits React and Next.js code for high-leverage runtime and rendering pitfalls, then routes to deep-dive references on useEffect anti-patterns, re-render causes, rendering model selection, React 19 APIs, and waterfall chains. Use when a .tsx or .jsx file is opened or reviewed, the user asks "is my React code good", mentions useEffect, re-renders, memoization, React Compiler, Server Components, Server Actions, SSR vs CSR, hydration, waterfalls, or bundle size. Triggers on React runtime/rendering reviews.

  • Refactor

    kriscard/Skills/skills/dev/refactor Skill

    16★ repo

    Performs behavior-preserving refactors to improve readability, reduce complexity, and enhance maintainability without altering functionality. Use when the user says "refactor", "simplify this code", "clean up", "reduce complexity", "extract method", "this is too complex", or asks to improve naming/structure without changing behavior. Preserves all public APIs unless explicitly authorized.

  • Research

    kriscard/Skills/skills/dev/research Skill

    16★ repo

    Fetches source-grounded, current docs for library/framework/API implementation. Use when the user needs API syntax, config options, examples, migration notes, or version-sensitive guidance. Do not invoke for stable concepts or broad explanations that can be answered from memory.

  • Review

    kriscard/Skills/skills/dev/review Skill

    16★ repo

    Bug-first, evidence-only review for code changes: find production-impacting security, correctness, reliability, performance, and maintainability issues. Use after writing or modifying code, when reviewing diffs or PRs, or when the user asks "review this", "check this code", mentions security, code quality, or performance. Enforces project guidance when available and prefers silence over speculative findings.

  • Spec

    kriscard/Skills/skills/dev/spec Skill

    16★ repo

    Creates an approval-gated spec for non-trivial feature work from an issue URL or requirements text. Use when the user asks for a spec/PRD, pastes a Linear, GitHub issue, or Jira URL, or requests implementation where scope is ambiguous enough to need acceptance criteria before coding.

  • Test

    kriscard/Skills/skills/dev/test Skill

    16★ repo

    Applies test-pyramid, red-green-refactor, and behavioral testing practices for common JS/Python/Ruby stacks and other projects after detecting the runner. Use when the user says "write tests", "add tests", "TDD", "test coverage", "this test is failing", or mentions Jest/Vitest/pytest/RSpec/Playwright/ Cypress. Also use when a feature is implemented without tests.

  • Audit

    kriscard/Skills/skills/dotfiles/audit Skill

    16★ repo

    Dotfiles health baseline and triage. Use when the user wants a whole-system audit of ~/.dotfiles: credential leaks, shell startup, Stow symlinks, Neovim startup, missing tools, or orphan config. Do not use for targeted Neovim or shell edits; route those to neovim or shell-env.

  • Neovim

    kriscard/Skills/skills/dotfiles/neovim Skill

    16★ repo

    Neovim config healthcheck for ~/.dotfiles/.config/nvim/ using lazy.nvim and GNU Stow. Use when the user wants to validate or repair Neovim, add/remove plugins, diagnose startup performance, fix keymaps/LSP, or modernize config. Prefer audit for whole-dotfiles reviews and shell-env for non-Neovim terminal config.

  • Shell env

    kriscard/Skills/skills/dotfiles/shell-env Skill

    16★ repo

    Stow-first shell environment editing for zsh, aliases, tmux/sesh, Starship, Ghostty, yabai, Git, and dotfiles packages. Use when the user wants to add or change terminal config, aliases, shell startup, or Stow-managed symlinks. Route Neovim-specific work to neovim and whole-system health checks to audit.

  • Learn

    kriscard/Skills/skills/learning/learn Skill

    16★ repo

    Socratic teaching for explicit learning requests: diagnose prior understanding, teach one concept at a time, verify comprehension, and correct misconceptions. Use for /learn, "teach me", or "I don't get X".

  • Til

    kriscard/Skills/skills/learning/til Skill

    16★ repo

    TIL capture for explicit requests to save learned material from a session into an engaging Obsidian note. Use when the user runs /til or asks to save, document, or write up what they learned.

  • Audit para

    kriscard/Skills/skills/obsidian/audit-para Skill

    16★ repo

    Read-only PARA classification audit for the Obsidian vault, followed by an optional explicit-fix flow. Use when the user asks to audit PARA, check whether notes are in the right place, find projects missing outcomes/deadlines, or runs /audit-para.

  • Capture receipt

    kriscard/Skills/skills/obsidian/capture-receipt Skill

    16★ repo

    Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.

  • Close day

    kriscard/Skills/skills/obsidian/close-day Skill

    16★ repo

    End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.

  • Daily

    kriscard/Skills/skills/obsidian/daily Skill

    16★ repo

    Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.

  • Goals

    kriscard/Skills/skills/obsidian/goals Skill

    16★ repo

    Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.

  • Ideas

    kriscard/Skills/skills/obsidian/ideas Skill

    16★ repo

    Idea capture and promotion for Obsidian: quick thoughts land in Inbox, conversation idea clusters are reviewed before writing, and daily-note ideas can be promoted to permanent notes. Use when the user asks to capture an idea, brain dump, write down a thought, find buried ideas, or graduate ideas from daily notes.

  • Ingest

    kriscard/Skills/skills/obsidian/ingest Skill

    16★ repo

    Source synthesis for Obsidian: ingest an article, URL, video, book note, or selected Inbox source into durable Resources notes after discussing the key ideas. Use when the user asks to ingest a source, add source material to the wiki, synthesize an article, or runs /ingest.

  • Maintain

    kriscard/Skills/skills/obsidian/maintain Skill

    16★ repo

    Runs a read-only health check on the Obsidian vault — finds broken links, orphaned notes, tag inconsistencies, and wiki issues, then reports prioritized fixes. Make sure to use this skill whenever the user says "vault health check", "fix broken links", "clean up my vault", "vault maintenance", or runs /maintain. Never modifies anything without explicit request — this skill diagnoses, it doesn't operate.

  • Memory recall

    kriscard/Skills/skills/obsidian/memory-recall Skill

    16★ repo

    Searches the Obsidian vault for prior knowledge, past decisions, and accumulated learnings — and finds unexpected connections between domains. Make sure to use this skill whenever the user asks "do I have notes on", "what do I know about", "what did I write about", "find in my vault", "check my notes about", "have I learned about", "what did I decide about", "connect [A] and [B]", "find bridges between", or any phrasing that implies consulting personal vault knowledge rather than answering from general knowledge. Also fires when user references prior sessions or wants to know what they already know about a topic.

  • Money

    kriscard/Skills/skills/obsidian/money Skill

    16★ repo

    Revenue advisor — scans the Obsidian vault for work history and active projects, diagnoses the revenue system, and surfaces monetization opportunities the user can't see from inside their own perspective. Make sure to use this skill whenever the user says "/money", "how can I make more money", "review my revenue", "what should I charge", "help me monetize", "find opportunities", or asks about income, pricing, or business strategy. Goes beyond the vault — diagnoses structure first, then surfaces opportunities.

  • Process inbox

    kriscard/Skills/skills/obsidian/process-inbox Skill

    16★ repo

    PARA triage for Obsidian Inbox notes: read each raw inbox note, suggest the correct PARA destination, confirm with the user, and move only on approval. Use when the user asks to process, clear, sort, or triage inbox notes, or runs /process-inbox.