agentsclimarketplace

Data & backend

10,137 rows, by stacks then stars

233 of these skill files have been read, by 258 distinct authors, and what they tell an agent counted. What Data & backend authors agree on, and what they forbid

  • Recall ai integration

    Rijul1204/rashedul-agentic-engineering/skills/recall-ai-integration Skill

    2★ repo

    Meeting-bot vendor integration knowledge — Recall.ai (bot dispatch + webhooks) plus closely-coupled ElevenLabs surfaces (Scribe as Recall's transcription provider, Voice as the TTS swap target). Use when the user asks to touch, extend, debug, or explain anything that calls the Recall.ai or ElevenLabs API or handles their webhooks. Fires on Recall.ai terms (RECALL_API_KEY, in_call_recording, output_audio, send_chat_message, transcript.data, bot.in_call_recording, bot.in_waiting_room, bot.call_ended, bot.fatal, Svix signature, realtime endpoint, sandbox region, us-west-2.recall.ai), ElevenLabs terms (Scribe, Voice, elevenlabs_streaming, elevenlabs_async, scribe_v2, ELEVENLABS_API_KEY, xi-api-key, voice_id, eleven_multilingual_v2), and on any new code that dispatches a bot, pushes audio, sends a chat message, or ends a bot. Enforces docs→fixture→probe→code, tri-site nesting consistency, doc-check date stamps at every call site, spec-faithful webhook fixtures with at least two events, and your repo's standard quality gates.

  • Shopify development

    display-design-studio/skills/skills/shopify-development Skill

    no license2★ repo

    Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid. TRIGGER: "shopify", "shopify app", "checkout extension", "admin extension", "POS extension", "shopify theme", "liquid template", "polaris", "shopify graphql", "shopify webhook", "shopify billing", "app subscription", "metafields", "shopify functions"

  • Firecrawl crawl

    arch3rPro/ark-space/plugins/ark-space/skills/firecrawl-crawl Skill

    2★ repo

    Use when bulk extracting a website or site section through Firecrawl CLI, especially docs sections, many pages on one site, or ArkSpace web_crawl routing that selects Firecrawl.

  • Tavily crawl

    arch3rPro/ark-space/plugins/ark-space/skills/tavily-crawl Skill

    2★ repo

    Use when crawling a website section through Tavily Crawl to collect content from many pages, download docs, bulk extract pages, or apply path/domain filters with extraction controls.

  • Firecrawl crawl

    arch3rPro/ark-space/skills/firecrawl-crawl Skill

    2★ repo

    Use when bulk extracting a website or site section through Firecrawl CLI, especially docs sections, many pages on one site, or ArkSpace web_crawl routing that selects Firecrawl.

  • Tavily crawl

    arch3rPro/ark-space/skills/tavily-crawl Skill

    2★ repo

    Use when crawling a website section through Tavily Crawl to collect content from many pages, download docs, bulk extract pages, or apply path/domain filters with extraction controls.

  • Db whisperer

    mturac/hermes-supercode-skills/skills/db-whisperer Skill

    2★ repo

    Diagnoses and improves application-layer databases: Postgres, MySQL, SQLite, and MongoDB. Covers EXPLAIN ANALYZE, slow query detection, index strategy, N+1 detection, schema migrations with up/down scripts, connection pooling, replication setup, and vacuum/analyze operations. Use this skill when the user says "this query is slow," "add an index for," "migration for a new column," "N+1 on this ORM," "explain this query plan," "replication lag," "optimize my database," "query is timing out," or "connection pool exhausted."

  • Ghost scraper

    mturac/hermes-supercode-skills/skills/ghost-scraper Skill

    2★ repo

    Extracts structured data from websites — static HTML, JavaScript-rendered SPAs, paginated listings, and API-backed pages. Handles anti-bot detection awareness, rate limiting, and robots.txt compliance. Use this skill whenever the user wants to scrape a website, extract data from a URL, pull product listings, harvest structured data, reverse-engineer a site's API, or deal with dynamic JS-rendered content. Also triggers on "get me data from this site," "extract prices from," "crawl these pages," or any request involving web data extraction, even casual ones like "can you pull info from this URL."

  • Pipeline architect

    mturac/hermes-supercode-skills/skills/pipeline-architect Skill

    2★ repo

    Designs and implements data pipelines: ETL/ELT, streaming, batch processing, schema migrations, and data warehouse architecture. Covers Kafka, Airflow, dbt, Spark, ClickHouse, BigQuery, Snowflake, Redis Streams, and more. Use this skill when the user asks about data pipelines, ETL jobs, data transformation, streaming setup, data warehouse design, CDC, schema migrations, data quality checks, or anything involving moving data from source to target. Also triggers on "build a pipeline," "migrate data from X to Y," "set up streaming," "design my data warehouse," or "data quality is bad, help me fix it."

  • Schema migration safety

    yuchi-chang/no-cape/skills/schema-migration-safety Skill

    no license2★ repo

    Use when writing database schema migrations or changing tables, columns, indexes, or constraints on a system with real data

  • Nestjs database

    FilippoDeSilva/skills/skills/nestjs/nestjs-database Skill

    no license2★ repo

    Implement data access patterns, Scaling, Migrations, and ORM selection in NestJS. Use when implementing TypeORM/Prisma repositories, migrations, or database patterns in NestJS.

  • Nestjs security

    FilippoDeSilva/skills/skills/nestjs/nestjs-security Skill

    no license2★ repo

    Implement JWT authentication, RBAC guards, Helmet hardening, and Argon2 hashing in NestJS. Use when adding auth strategies, role-based access control, CSRF protection, or security headers.

  • Nestjs transport

    FilippoDeSilva/skills/skills/nestjs/nestjs-transport Skill

    no license2★ repo

    Configure gRPC, RabbitMQ, and monorepo contract patterns for NestJS microservices. Use when setting up gRPC service-to-service calls, RabbitMQ event-driven messaging, shared contract libraries, or microservice exception handling in NestJS.

  • Nextjs authentication

    FilippoDeSilva/skills/skills/nextjs/nextjs-authentication Skill

    no license2★ repo

    Secure token storage (HttpOnly Cookies) and Middleware patterns. Use when implementing authentication, secure session storage, or auth middleware in Next.js.

  • Nexus backend serverless

    Shuwanito/SkillsMP/.claude/skills/nexus-backend-serverless Skill

    no license2★ repo

    Serverless and microservices engineering agent. Use when you need to design FaaS architectures, build event-driven microservices, optimize cold start times, control serverless costs, or evaluate serverless platforms and patterns for scalable applications.

  • Nexus backend

    Shuwanito/SkillsMP/.claude/skills/nexus-backend Skill

    no license2★ repo

    Backend architecture agent specializing in high-performance APIs, microservices, and data integrity. Use when you need to design or review API architectures, optimize database queries, identify security vulnerabilities and performance bottlenecks, or evaluate backend patterns for FastAPI and SQLAlchemy.

  • Nexus data engineer

    Shuwanito/SkillsMP/.claude/skills/nexus-data-engineer Skill

    no license2★ repo

    Data engineering agent specializing in ETL/ELT pipelines, data quality, warehousing, and streaming. Use when you need to design or review data pipelines, ensure data integrity, detect schema drift, or evaluate tools like dbt, Airflow, and streaming platforms for EdTech and enterprise workloads.

  • Nexus security auditor

    Shuwanito/SkillsMP/.claude/skills/nexus-security-auditor Skill

    no license2★ repo

    Comprehensive security audit agent. Performs OWASP Top 10 checks, dependency vulnerability scanning, authentication/authorization review, and penetration testing recommendations.

  • Nexus security auditor

    Shuwanito/SkillsMP/huggingface/nexus-security-auditor Skill

    no license2★ repo

    Comprehensive security audit agent. Performs OWASP Top 10 checks, dependency vulnerability scanning, authentication/authorization review, and penetration testing recommendations.

  • Docker dev environment

    martian56/claude-engineer/plugins/claude-engineer/skills/docker-dev-environment Skill

    2★ repo

    Use when setting up local development services or running the project locally. Establishes the "stateful services in Docker, app runs native" pattern with Postgres, Redis, MinIO, and Mailpit.

  • Database

    ndisisnd/cook/standards/database Skill

    2★ repo

    Database standards for PostgreSQL persistence and Redis caching. Use when designing schemas, writing migrations, optimizing queries, configuring Redis, or implementing cache invalidation.

  • Graphql

    ndisisnd/cook/standards/graphql Skill

    2★ repo

    GraphQL schema design standards and resolver conventions. Use when writing or reviewing any GraphQL schema, resolver, or operation — naming, nullability, types, input objects, mutations, queries, and operation structure.

  • Supabase

    ndisisnd/cook/standards/supabase Skill

    2★ repo

    Supabase platform standards — Row-Level Security, publishable/anon and secret/service_role key boundaries, Postgres and Edge functions, Storage, Realtime, and the CLI migration workflow. Use when working with RLS policies, Supabase clients, Edge Functions, or supabase/ migrations. Loads alongside the database (Postgres) domain.

  • Mongodb

    fworks-tech/agenthood/skills/mongodb Skill

    2★ repo

    Manage MongoDB databases via the mongosh CLI. Use when querying, inspecting, or managing MongoDB collections.

  • Mysql

    fworks-tech/agenthood/skills/mysql Skill

    2★ repo

    Manage MySQL databases via the mysql CLI. Use when querying, inspecting schema, or managing MySQL databases.

  • Postgres

    fworks-tech/agenthood/skills/postgres Skill

    2★ repo

    Manage PostgreSQL databases via the psql CLI. Use when querying, inspecting schema, or managing PostgreSQL databases.

  • Redis

    fworks-tech/agenthood/skills/redis Skill

    2★ repo

    Manage Redis via the redis-cli. Use when interacting with Redis caches, queues, or key-value stores.

  • Fastapi senior dev

    hackermanishackerman/claude-skills-vault/.claude/skills/fastapi-senior-dev Skill

    2★ repo

    Senior Python Backend Engineer skill for FastAPI. Use when scaffolding production-ready APIs, enforcing clean architecture, optimizing async patterns, or auditing FastAPI codebases.

    The same file is in 1 other repository

  • Scaffold backend

    IdkwhatImD0ing/hackathonstarterkit/.agents/skill-improvement-workspace/baseline-skills/scaffold-backend Skill

    no license2★ repo

    PRD-driven backend scaffold. Reads AGENTS.md and PRD.md from the repo root and creates a FastAPI app inside server/ with optional Supabase integration and one stub route per entry listed under PRD.md > Backend Routes. Refuses to run if AGENTS.md and PRD.md do not exist, or if PRD.md says Backend Needed? = No. Run AFTER scaffold-frontend.

  • Scaffold backend

    IdkwhatImD0ing/hackathonstarterkit/.agents/skills/scaffold-backend Skill

    no license2★ repo

    Create a PRD-driven FastAPI backend in `server/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after frontend scaffolding only when `PRD.md` says `Backend Needed?` is Yes, especially for API routes, Pydantic models, health checks, optional Supabase wiring, and type-safe placeholder data.

  • Prisma access audit

    vahagn-madatyan/netsec-skills-suite/skills/prisma-access-audit Skill

    2★ repo

    Palo Alto Prisma Access SASE audit — security policy evaluation for mobile users and remote networks, GlobalProtect Cloud Service configuration review, service connection validation, threat prevention profile assessment, and Strata Cloud Manager posture analysis across Prisma Access tenants.

  • Guardrails

    jacob-balslev/skills/skills/ai-engineering/guardrails Skill

    2★ repo

    Use when planning or executing agent/tool operations that touch protected files, credentials, destructive git commands, destructive SQL, PII, secrets, deployments, package publication, or irreversible system mutations. Covers proactive safety policy, tool-call tripwires, blocking vs advisory enforcement, secret-exposure prevention, and excessive-agency containment. Do NOT use for application input validation, routine git workflow design, migration authoring, or general code correctness review (use `code-review`, `version-control`, or `database-migration`).

  • Caching strategies

    jacob-balslev/skills/skills/backend-engineering/caching-strategies Skill

    2★ repo

    Deciding what to cache, where, and how to keep it coherent — trading freshness for speed and load reduction across the cache layers (client, CDN/edge, application in-memory, distributed cache, database). Covers the two hard problems (cache invalidation and choosing the layer), the write/read patterns (cache-aside/lazy, read-through, write-through, write-behind, refresh-ahead), expiry and TTL design, eviction policies (LRU/LFU/FIFO/TTL), staleness budgets and tolerated inconsistency, cache coherence and invalidation strategies (TTL expiry, explicit invalidation, key/tag versioning, write-through), the thundering-herd / cache-stampede problem and its mitigations (request coalescing, locks, jitter, stale-while-revalidate), HTTP caching semantics (Cache-Control, ETag, conditional requests, stale-while-revalidate/stale-if-error), CDN and edge caching, multi-layer cache hierarchies, cache key design and cardinality, negative caching, and measuring hit ratio and the cost of a miss. Stack-agnostic across Redis/Memcached, CDNs, browser cache, and framework data caches.

  • Connection pooling

    jacob-balslev/skills/skills/backend-engineering/connection-pooling Skill

    2★ repo

    Use when reasoning about how an application manages its database connections: why every connection has a server-side cost, the difference between application-level pools (HikariCP, pgx pool, node-postgres Pool) and proxy-level pools (PgBouncer, Pgpool, ProxySQL), the three PgBouncer modes (session, transaction, statement) and their feature compatibility, the canonical pool-sizing math (Little's Law applied to database concurrency; Wooldridge's analyses), the failure modes (connection exhaustion, hot-loop reconnects, prepared-statement breakage under transaction pooling, idle-in-transaction leaks), and the diagnostic procedure when a workload is contending on connections instead of query work. Do NOT use for query-level performance (use query-optimization), for index design (use indexing-strategy), for read/write replica routing (use replication-patterns), or for cross-shard query coordination (use sharding-strategy).

  • Route handler design

    jacob-balslev/skills/skills/backend-engineering/route-handler-design Skill

    2★ repo

    Use when designing or reviewing Next.js Route Handlers (the `route.ts`/`route.js` file convention in App Router): when a Route Handler is the right public HTTP endpoint surface vs Server Actions or Server Components, the HTTP-method-as-export contract (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS), the Web-standard Request/Response interface (no Node `req`/`res`), the body-parsing primitives (`request.json`/`formData`/`text`/`blob`/`arrayBuffer`) and one-shot body consumption, the default caching behavior of GET responses (NOT cached by default since Next 15; opt IN via `dynamic = 'force-static'`) and the Cache Components `use cache` model, async `params`/`cookies`/`headers` and `RouteContext` typed params, dynamic segments and search params, the rule that every Route Handler is a PUBLIC surface that must authenticate/authorize/validate inside the handler, manual CORS, runtime/deployment selection (Node default and recommended after Vercel folded standalone Edge Functions onto Vercel Functions; the Edge runtime still selectable; `maxDuration`/`preferredRegion`/static-export limits), streaming via `ReadableStream` including `pull()` backpressure, status-code and header discipline, error responses, webhook-style handlers (signature verify before parse, ACK fast, `after()` for short post-response work), and the design rule that a Route Handler is the right surface when the caller is not your own Next.js UI. Do NOT use for internal mutations triggered from your own UI (use server-actions-design), for render-time reads from your own Server Components (call the data source directly), for the broader REST/contract/versioning discipline (use api-design), for HTTP method/status semantics in the abstract (use http-semantics), for request preprocessing across all routes — now `proxy.ts`/`middleware.ts` (use middleware-patterns), or for the broader webhook reliability story — HMAC verification, idempotency, retries, queue handoff (use webhook-integration).

  • Transaction isolation

    jacob-balslev/skills/skills/backend-engineering/transaction-isolation Skill

    2★ repo

    Use when reasoning about the I in ACID: the isolation level a database provides between concurrent transactions; the four SQL-standard levels plus practical snapshot/read-versioning modes; the anomalies each level can admit or prevent; the Berenson/Adya critique of label-based isolation; locking, MVCC, row-versioning, SSI, key-range/gap/predicate locks, RCSI, and distributed-SQL serializable/external-consistency defaults; and how to choose isolation per workload by naming the anomalies, invariants, retry contract, and engine-specific behavior. Do NOT use for the broader ACID frame (outside this active skill corpus), distributed-replica consistency or CAP/PACELC choices (use cap-theorem-tradeoffs and replication-patterns), query performance tuning (use query-optimization), durable index design (use indexing-strategy), or schema design (use entity-relationship-modeling).

  • Webhook integration

    jacob-balslev/skills/skills/backend-engineering/webhook-integration Skill

    2★ repo

    Use when implementing or reviewing an inbound webhook handler for any third-party provider - verifying signatures, deduplicating retries, choosing the right HTTP status code for retry vs no-retry, persisting raw payloads before canonical mapping, and quarantining unverifiable events. Covers signature schemes, idempotency patterns, provider retry contracts, raw-then-canonical pipelines, quarantine, secret rotation, and PII-capture timing. Do NOT use for outbound webhook publishing (use `event-contract-design`), general background-job orchestration, or chasing a webhook handler that has already failed in production (use `debugging`).

  • Data modeling fundamentals

    jacob-balslev/skills/skills/data-engineering/data-modeling-fundamentals Skill

    2★ repo

    Use when reasoning about the theory beneath data modeling: Codd's relational model and algebra, normal forms from 1NF through 5NF/BCNF, functional dependencies and closure, Chen ER modeling, principled denormalization, relational-vs-document tradeoffs, and immutable-data alternatives such as event sourcing or append-only tables. Do NOT use for practical persistence design (use entity-relationship-modeling), applying schema changes (use schema-evolution), index choices (use indexing-strategy), or conceptual modeling above the data model (use conceptual-modeling).

  • Database migration

    jacob-balslev/skills/skills/data-engineering/database-migration Skill

    2★ repo

    Use when planning or applying a raw-SQL database migration to a live PostgreSQL database — adding columns, renaming columns or tables, changing types, creating indexes, adding foreign keys, or running data backfills. Covers zero-downtime patterns (expand / contract, batched backfill, NOT VALID foreign keys, CONCURRENTLY indexes), the direct/unpooled connection requirement for migration tooling, branched-database workflows, and rollback strategy. Do NOT use for ORM-managed migrations driven by Prisma/Drizzle/TypeORM CLI scaffolding, for chasing a migration that has already failed in production (use debugging), for multi-release schema lifecycle planning outside one migration (use schema-evolution), or for designing the row-level-security model itself (use owasp-security).

  • Indexing strategy

    jacob-balslev/skills/skills/data-engineering/indexing-strategy Skill

    2★ repo

    Use when designing or auditing the maintained index set for a database workload: choosing index structures, matching access patterns, setting composite order, balancing read speed against write/storage cost, and deciding when to add, keep, or drop indexes. Do NOT use for tuning one slow query (use query-optimization), applying production DDL (use database-migration), isolation choices, schema design, or sharding.

  • Query optimization

    jacob-balslev/skills/skills/data-engineering/query-optimization Skill

    2★ repo

    Diagnosing and tuning a specific slow relational-database query from plan evidence: workload impact, exact query context, EXPLAIN / actual execution plans, row-estimate accuracy, access path choice, join order, sort/hash spills, JIT/planning overhead, parameter-sensitive plans, plan regressions, statistics, and rewrite-vs-index-vs-operational response selection. Start from the actual plan and runtime evidence, not from the reflex to add an index; modern engine features such as Query Store, PSP/OPPO, SQL Plan Management, pg_stat_statements, auto_explain, MySQL histograms, Oracle DBMS_XPLAN, and PostgreSQL planner improvements are evidence sources and response tools, not replacements for diagnosis. Do NOT use for designing the durable index portfolio (use indexing-strategy), schema design (use entity-relationship-modeling), distributed partitioning (use sharding-strategy), isolation-level correctness (use transaction-isolation), or whole-system load testing (use performance-testing).

  • Replication patterns

    jacob-balslev/skills/skills/data-engineering/replication-patterns Skill

    2★ repo

    Use when designing how a database keeps multiple copies of its data in agreement across nodes for availability, read scaling, and disaster recovery: the three foundational topologies (single-leader / primary-replica, multi-leader / multi-primary, leaderless / quorum), synchronous vs asynchronous replication and the replication-lag trade-off, log shipping vs statement replication vs trigger-based replication, the read-after-write consistency problem and its mitigations (sticky session, read-from-leader, monotonic reads), the failover model and split-brain risk, and the relationship to the CAP/PACELC choices the topology realizes. Do NOT use for horizontal partitioning across nodes (use sharding-strategy), the CAP theoretical frame itself (use cap-theorem-tradeoffs), single-node transactional guarantees (use transaction-isolation), or query tuning (use query-optimization).

  • Schema evolution

    jacob-balslev/skills/skills/data-engineering/schema-evolution Skill

    2★ repo

    Use when reasoning about how a database schema changes over time without breaking deployed application code — the multi-release path from the current schema to a target schema: the expand/contract pattern (Ambler & Sadalage / Fowler's parallel change), the zero-downtime change rules, the backwards-and-forwards compatibility envelope (deploy ordering and rollback discipline), the catalog of schema changes (add column, drop column, rename, type change, add constraint, add index) and the safe procedure for each, the dual-write and dual-read transitions (with named source-of-truth and production consistency-check discipline) that make non-trivial changes safe, the lock-acquisition hazard (why even a metadata-only DDL needs a bounded lock-acquisition budget — Postgres lock_timeout + retry, or the engine equivalent — because lock acquisition is a FIFO queue), the cross-engine online-change mechanisms (Postgres CONCURRENTLY / NOT VALID, MySQL INSTANT/INPLACE/COPY Online DDL, gh-ost / pt-osc ghost-table cutover, Vitess/PlanetScale deploy requests and revert windows), the view-based multi-version tooling that automates expand/contract (pgroll, Reshape), the migration-lint enforcement layer (Strong Migrations, Squawk, Atlas), and the relationship between schema evolution as a design discipline and database-migration mechanics as its tooling. Do NOT use for the mechanical execution of one migration (use database-migration), schema design from scratch (use entity-relationship-modeling), query tuning (use query-optimization), or distributed-data partitioning (use sharding-strategy).

  • Server actions design

    jacob-balslev/skills/skills/frontend-engineering/server-actions-design Skill

    2★ repo

    Use when designing or reviewing React Server Functions / Next.js Server Actions for mutations: the 'use server' directive, function-to-POST endpoint semantics, form integration through action/formAction, React useActionState and useFormStatus, progressive enhancement, server-side validation, authentication, authorization, rate limiting, cache revalidation, redirect/refresh/updateTag behavior, bound arguments, and the security boundary that makes actions public HTTP endpoints despite function-like syntax. Covers Next.js App Router as the canonical implementation. Do NOT use for read-path data fetching with React Server Components (use server-components-design), broader serialization/directive mechanics (use client-server-boundary), externally consumed API contracts (use api-design), or form visual/interaction UX (use form-ux-architecture).

  • Printify

    jacob-balslev/skills/skills/product-domain/printify Skill

    2★ repo

    Use when working with Printify — the print-on-demand REST API, catalog model (blueprints, print providers, variants, print areas), product creation and publish lifecycle to connected channels, order routing, shipping cost queries, and HMAC SHA-256 webhook verification. Do NOT use for non-Printify POD vendors, generic Shopify storefront work, or print-file (artwork) generation.

  • Shopify

    jacob-balslev/skills/skills/product-domain/shopify Skill

    2★ repo

    Use when working with Shopify — Admin API, Storefront API, OAuth scopes, HMAC SHA-256 webhook verification, GraphQL query-cost handling, Online Store 2.0 themes (sections, blocks, Liquid), metafields and metaobjects, and App Proxy. Do NOT use for generic e-commerce design, non-Shopify storefronts, or internal event-contract design.

  • Owasp security

    jacob-balslev/skills/skills/quality-assurance/owasp-security Skill

    2★ repo

    Use when reviewing code for security vulnerabilities, threat-modelling a new feature, implementing authentication or authorization, handling user input, hardening dependencies or CI/CD against software-supply-chain compromise, or auditing a codebase against the current OWASP Top 10 (2025, with the 2021 mapping retained). Covers broken access control (incl. SSRF), security misconfiguration, software supply chain failures, cryptographic failures, injection (SQL, NoSQL, command, LDAP, XSS), insecure design, authentication failures, software/data integrity failures, security logging and alerting failures, and mishandling of exceptional conditions (fail-open error paths, error leakage). Do NOT use for general code review (use `code-review` for the holistic per-PR pass), for chasing a known production bug (use `debugging`), for defending an LLM against prompt/RAG injection or agent-tool-authority abuse (use `prompt-injection-defense`), or for writing a security policy doc (use `documentation`).

  • Security fundamentals

    jacob-balslev/skills/skills/quality-assurance/security-fundamentals Skill

    2★ repo

    Use when reasoning about baseline application-security properties: threat modeling, trust boundaries, Saltzer and Schroeder design principles, input validation, authentication vs authorization, secrets handling, secure-by-default choices, least privilege, defense in depth, and OWASP vulnerability classes as recurring failure modes. Covers cross-cutting decisions about what is trusted, where validation belongs, where authn/authz checks live, and how to bound blast radius. Do NOT use for LLM-specific prompt injection or agent-tool authority (use prompt-injection-defense), OWASP-category deep code review (use owasp-security), vendor webhook mechanics (use webhook-integration), cryptographic primitive implementation or key-management mechanics (use vendor/KMS/library docs), compliance/legal artifacts, or the social/organizational side of security.

  • Entity relationship modeling

    jacob-balslev/skills/skills/software-architecture/entity-relationship-modeling Skill

    2★ repo

    Use when designing database tables, reviewing schema changes, planning migrations, or translating conceptual models into physical database structures. Covers ER notation, entity/attribute/key design, normalization and denormalization, junction tables, inheritance mapping, temporal modeling, ER-to-SQL translation, indexing, and constraints. Do NOT use for conceptual domain analysis (use `conceptual-modeling`), formal ontology (use `ontology`), or cross-system API contracts (use `system-interface-contracts`).

  • Event contract design

    jacob-balslev/skills/skills/software-architecture/event-contract-design Skill

    2★ repo

    Use when designing or reviewing asynchronous event contracts: producer/consumer ownership, event envelope, schema, topic/channel naming, ordering, idempotency, versioning, compatibility, replay, dead-letter behavior, and AsyncAPI/CloudEvents-style documentation. Do NOT use for domain-event discovery (use `event-storming`), broad interface contracts (use `system-interface-contracts`), inbound provider webhook mechanics (use `webhook-integration`), or HTTP endpoint design (use `api-design`).

  • Wassenger webhooks

    wassengerhq/whatsapp-skills/skills/wassenger-webhooks Skill

    2★ repo

    Subscribe to real-time WhatsApp events from Wassenger — inbound messages, delivery and read receipts, status changes, campaign events, chat assignment changes, device state, and more. Use when the user wants live automation triggered by WhatsApp events (auto-replies, CRM sync, alerting, opt-out handling, multi-agent routing). Covers subscription via the REST API, payload shapes, HMAC signature verification, retries, and how to expose a public endpoint locally for development.

  • Write sql

    a-novel-kit/stack/.agents/skills/write-sql Skill

    2★ repo

    Write, review, and maintain PostgreSQL SQL for Agora backend services. Use whenever creating or editing SQL — DAO query files (internal/dao/*.sql), schema migrations (internal/models/migrations/*.sql), or raw SQL embedded in Go: SELECT/INSERT/UPDATE/DELETE queries, DDL (tables, views, indexes, constraints), materialized views, pg_cron jobs.

  • Api producer

    morning-start/agent-skills/process/doc-orchestrator/skills/doc-phase-production/api-producer Skill

    no license2★ repo

    Use when the user needs API documentation for RESTful, GraphQL, or gRPC interfaces.

  • Python team

    morning-start/agent-skills/process/python-team Skill

    no license2★ repo

    通过自主学习、PM、架构师、高级程序员四角色协同,从自然语言需求自动生成完整Python项目交付物。支持功能扩展、项目重构、技能调用。支持网络搜索、知识整合、版本控制、Python 3.11+特性、UV包管理、loguru日志、项目规模自适应(文件夹/单文件)。支持数据库设计与实现(SQLite、PostgreSQL、MongoDB、向量数据库、图数据库)、数据层抽象(Repository 模式)、数据库切换。适用于软件需求澄清、快速原型开发、项目初始化、功能扩展、代码重构等场景。

  • Airflow dag patterns

    newmindsgroup/ai-agent-skills-library/dist/skills/airflow-dag-patterns Skill

    2★ repo

    Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.

  • Api endpoint builder

    newmindsgroup/ai-agent-skills-library/dist/skills/api-endpoint-builder Skill

    2★ repo

    Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.

  • Api security best practices

    newmindsgroup/ai-agent-skills-library/dist/skills/api-security-best-practices Skill

    2★ repo

    Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities

  • Api security testing

    newmindsgroup/ai-agent-skills-library/dist/skills/api-security-testing Skill

    2★ repo

    API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.

  • Apify ultimate scraper

    newmindsgroup/ai-agent-skills-library/dist/skills/apify-ultimate-scraper Skill

    2★ repo

    AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.

  • Auth implementation patterns

    newmindsgroup/ai-agent-skills-library/dist/skills/auth-implementation-patterns Skill

    2★ repo

    Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.