agentsclimarketplace

Ship & operate

32,344 rows, by stacks then stars

1,245 of these skill files have been read, by 1,077 distinct authors, and what they tell an agent counted. What Ship & operate authors agree on, and what they forbid

  • Scan project

    AayushMS/deploy-skills/skills/scan-project Skill

    0★ repo

    Use this skill when the user asks to "scan my project", "analyze my project", "what does my project need to run", "find all services in my project", "document how to run my project", "understand my project structure", "detect services in my codebase", "what frameworks does my project use", "analyze my codebase for deployment", or when invoked by the deploy-project orchestrator as the first step before deployment. This skill reads the project codebase, detects all services (frontend, backend, database, queues, workers), recommends free deployment platforms for each service, and writes three documentation files to DEPLOYMENT_DOCS/.

  • Setup auth

    AayushMS/deploy-skills/skills/setup-auth Skill

    0★ repo

    Use this skill when the user asks to "set up auth for deployment", "log in to deployment tools", "authenticate deployment tools", "check if I'm logged into Vercel/Railway/Supabase/etc", "set up credentials for deploying", or when invoked by the deploy-project orchestrator after scan-project to authenticate all required deployment platforms before deploying. Reads DEPLOYMENT_DOCS/DEPLOYMENT_PLAN.md to determine which tools are needed, then verifies and guides login for only those tools.

  • Setup cicd

    AayushMS/deploy-skills/skills/setup-cicd Skill

    0★ repo

    Use this skill when the user asks to "set up CI/CD", "create GitHub Actions", "automate my deployments", "set up auto-deploy on push", "create deployment workflows", or when invoked by the deploy-project orchestrator after all services are deployed to set up GitHub Actions workflows. Reads DEPLOYMENT_DOCS/DEPLOYMENT_PLAN.md and DEPLOYMENT_DOCS/DEPLOYED_ENV.md to know what was deployed, generates .github/workflows/ files appropriate for the platforms used, stores deploy tokens as GitHub Secrets via `gh secret set`, and commits + pushes the workflows.

  • Verify deployment

    AayushMS/deploy-skills/skills/verify-deployment Skill

    0★ repo

    Use this skill when the user asks to "verify my deployment", "check if everything is working", "test my deployment", "check if my services are up", "run health checks", or when invoked by deploy-project as the final step after CI/CD setup. Reads DEPLOYMENT_DOCS/DEPLOYED_ENV.md for service URLs, runs HTTP health checks on all services, uses agent-browser to visually verify the frontend loads, tests cross-service connectivity (frontend calls backend, backend connects to DB), and prints a pass/fail summary table. Retries Render backend endpoints up to 3 times due to free tier cold starts.

  • Workflow 6ayh

    awfaups/intake-governance/skills/workflow-6ayh Skill

    0★ repo

    6AO workflow detail layer for progressive optimization and refactor work after workflow selection is known. Use when the task is already confirmed as 6AO, the user explicitly requests @6AO or legacy alias @6AYH, or intake has classified the task as gradual optimization, refactoring, maintenance-cost reduction, or performance cleanup. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

  • Workflow generic governance

    awfaups/intake-governance/skills/workflow-generic-governance Skill

    0★ repo

    GGW workflow detail layer for role-based planning, review, dispatch, and closeout after intake has classified a task as generic_governance. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

  • Workflow ppw

    awfaups/intake-governance/skills/workflow-ppw Skill

    0★ repo

    PMW workflow detail layer for project inventory and process clarification after workflow selection is known. Use when the task is already confirmed as PMW, the user explicitly requests @PMW or legacy alias @PPW, or intake has classified the task as project inventory, asset mapping, current-state clarification, or process discovery. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

  • Workflow sdd

    awfaups/intake-governance/skills/workflow-sdd Skill

    0★ repo

    SDD workflow detail layer for specification-driven development after workflow selection is known. Use when the task is already confirmed as SDD, the user explicitly requests @SDD or legacy alias @sdd, or intake has classified the task as spec-first delivery where implementation, tests, and acceptance derive from an approved spec bundle. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

  • Setup ci

    stackql/stackql-skills/skills/setup-ci Skill

    0★ repo

    Generate CI/CD pipeline configuration for stackql-deploy stacks. Supports GitHub Actions. Creates workflows for build, test, and teardown of cloud infrastructure.

  • Ship

    jessedegans/jstack/skills/ship Skill

    no license0★ repo

    Use when shipping, deploying, creating a PR, or preparing a release. Review staleness detection, gated review requirement with override options, and a structured release flow. Use when: user says "ship it", "create a PR", "let's deploy", "ready to merge", or is preparing code for release.

  • Terraform platform engineer

    papanito/ai-skills/skills/terraform-platform-engineer Skill

    no license0★ repo

    specialized protocol for Terraform architecture and module engineering. Focuses on HCL 1.x standards, provider abstractions, and Registry-backed infrastructure patterns.

  • Rust ci deploy

    dawidpereira/rust-skills/skills/rust-ci-deploy Skill

    0★ repo

    CI pipelines, GitHub Actions, caching, cross-compilation, Docker builds, release automation, cargo-dist, cargo-audit, cargo-deny, static linking, musl. Trigger for CI/CD, deployment, and release tasks.

  • Rust tracing

    dawidpereira/rust-skills/skills/rust-tracing Skill

    0★ repo

    Rust observability with tracing — structured logging, spans, subscribers, and instrumentation. Use when choosing between tracing and log, setting up subscribers and layers, adding #[instrument] to functions, configuring RUST_LOG, instrumenting async code (.instrument() vs span.enter()), integrating tower-http or sqlx middleware, protecting sensitive data in logs, or preparing tracing for production with OpenTelemetry. Also use when reviewing code for logging quality or adding request correlation IDs.

  • Devops

    Victoriakaey/build-reliable-agents/skills/devops Skill

    0★ repo

    Use when deploying an application to production, setting up CI/CD, or moving from local development to a hosted environment. Guides through deployment target selection (PaaS, Docker+VPS, cloud platform), containerization, environment configuration, CI/CD pipeline design, monitoring, and rollback strategy. Covers both simple and complex deployment scenarios.

  • Release notes retriever

    jsynowiec/claude-toolkit/plugins/stackshift/skills/release-notes-retriever Skill

    0★ repo

    Fetches upstream release notes, changelogs, deprecation notices, and migration guides for a library or runtime version range. Use before analyzing API changes or planning upgrades.

  • Ship

    pedroberaldo87/pedro-plugins/plugins/ship/skills/ship Skill

    no license0★ repo

    Use quando o código está pronto pra ir pra produção — roda lint, type-check, commit, push e deploy num fluxo disciplinado. Dispara em "ship", "manda", "deploya tudo". No fim de um ciclo de implementação, OFEREÇA pra dar ship — nunca deploye por conta própria sem o usuário pedir.

  • Ci release maintainer

    alainlebret/claude-agents/higher-ed-teaching-agents/skills/ci-release-maintainer Skill

    0★ repo

    Maintains CI validation and release hygiene for workflows, skills, and tooling. Use when preparing stable updates or publishing new versions.

  • Workflow router

    alainlebret/claude-agents/higher-ed-teaching-agents/skills/workflow-router Skill

    0★ repo

    Selects the best workflow-spec dynamically from the repository, computes the minimal skill chain, and emits a deterministic routing decision with confidence and fallback. Use when the orchestrator receives a pedagogical request and must choose among multiple workflows without hardcoded chains.

  • Wp deploy without local

    OmarEltak/wp-rescue-kit/wp-deploy-without-local Skill

    0★ repo

    When you need to deploy WordPress changes (theme files, new plugins, content) but cannot use Local/staging because it's broken, and you don't have SSH/FTP access — only wp-admin in the browser. Covers Theme File Editor, Plugin Upload, Plugin File Editor, and CodeMirror automation tricks. Triggers on "deploy WordPress", "no SSH", "no FTP", "Local is broken", "edit theme via wp-admin", "upload plugin via wp-admin", "Theme File Editor", "Plugin File Editor".

  • Release window

    pagoda111king/claude-code-pack/template/.claude/skills/release-window Skill

    no license0★ repo

    Release window planning · Solo Founder edition production-scheduling. Combines local holidays, niche industry peak/off seasons, and personal energy cycles to recommend optimal launch and major version release timing for each product. Use when a founder asks "when to ship", "which week to schedule", or "is now a good time to release".

  • Ship checklist

    pagoda111king/claude-code-pack/template/.claude/skills/ship-checklist Skill

    no license0★ repo

    Pre-launch checklist. Use before shipping a product or feature to external users. Solo Founder edition (not enterprise), trimmed to under 20 items to prevent real blockers that could sink you.

  • Trueprofit blog triggers

    khanhvo2172-dotcom/seo-skills/trueprofit-blog-triggers Skill

    0★ repo

    Recheck a TrueProfit blog Google Doc and add the CMS "highlight triggers" the n8n publishing workflow needs before a post can be built: a Content Highlight label above formulas and Pro tip/Note callouts, and Image trigger lines with auto-numbered be.trueprofit.io CDN URLs - and it reports whether the Quick Recap and FAQ sections exist. Use this whenever the user asks to "check", "prep", "recheck", "add triggers to", or "get ready for publish" a blog Google Doc, mentions Content Highlight / Quick Recap / FAQ / Image triggers / sentence notes, gives a Google Docs link for the TrueProfit blog pipeline, or is about to push a doc through the n8n blog automation. Edits the doc in place via the Google Docs API, first tab only. Prefer this skill over editing the doc by hand or eyeballing the triggers.

  • Loadout dev

    missionbuilt/loadout/skills/loadout-dev Skill

    0★ repo

    Expert development partner for The Loadout — the Mission Built MCP server (mcp.missionbuilt.io) that powers The Warmup and The Spotter skills. Use this skill any time you are working on the Loadout project: adding or editing a skill, modifying warmup-template.html or spotter-template.html, changing index.ts tools, bumping versions, editing SKILL.md files, running a tech lead review, or preparing a commit and deploy. Also use it when the user says things like "work on the warmup," "add a new loadout skill," "update the spotter," "edit the template," "bump the version," or "review before we ship." This skill carries the full project architecture, hard-won lessons from past sessions, and the exact collaboration model Mike and Claude use — including the rule that Mike runs all terminal commands and Claude writes all code. DO NOT invoke for end-user requests to RUN the skills — "spot my epic," "run my warmup," "run the approach for [company]" are handled by the MCP tools directly, not by this development skill.

  • Cron dispatch

    baronguyen001/ai-automation-skills/skills/cron-dispatch Skill

    0★ repo

    Schedule any script to run on a recurring schedule on Windows (Task Scheduler) or Linux (cron) - register, list, and remove jobs from one command, with logging to a file and a guard against overlapping runs. Use for schedule a script, run nightly, set up a cron job, windows task scheduler, or run on a timer.

  • Ship epic gh

    semanticpixel/abc/plugins/abc/skills/ship-epic-gh Skill

    0★ repo

    GitHub · GitHub-Issues sibling of /abc:ship-epic. Coordinator for a GitHub parent issue whose children live in a managed `## Sub-issues` task-list. Builds a dependency graph from `blocks:#N` / `blocked-by:#N` labels on the children, fires `/loop 6m /abc:ship-issue-gh <owner>/<repo>#<n>` per ready child (truly parallel via independent cron entries), gates blocked children until upstreams merge, aggregates status into the parent. Self-arms its own `/loop` — invoke once and walk away. TRIGGER when the user says "/ship-epic-gh <owner>/<repo>#<n>", asks to "ship this epic" against a GitHub parent, or wants to drive a multi-repo GitHub epic through merge in parallel.

  • Ship epic

    semanticpixel/abc/plugins/abc/skills/ship-epic Skill

    0★ repo

    Linear · Coordinator for a Linear parent issue whose sub-issues span multiple repos. Builds a dependency graph from sub-issue `blocks`/`blocked by` relations, fires `/loop /abc:ship-issue <SUB-ID>` per ready sub-issue (truly parallel via independent cron entries), gates blocked sub-issues until upstreams merge, aggregates status into the parent. Self-arms its own `/loop` — invoke once and walk away. TRIGGER when the user says "/ship-epic PARENT-ID", asks to "ship this epic", or wants to drive a Linear parent through merge in parallel across repos.

  • Ship issue gh

    semanticpixel/abc/plugins/abc/skills/ship-issue-gh Skill

    0★ repo

    GitHub · GitHub-Issues sibling of /abc:ship-issue. Drives a GitHub issue (or list, or parent with task-list children) from `pending` to `merged` through the implement → PR → address-review → merge loop. Emulates Linear's state machine on top of GitHub Issues using the label conventions documented in scaffold-sub-issues-gh/github-conventions.md. TRIGGER when the user says "/ship-issue-gh <owner>/<repo>#<n>", asks to ship/land/drive a GitHub issue, or wants Claude to take a GitHub-tracked ticket through review to merge. Also trigger when resuming work on a GitHub issue with an open PR and pending reviewer comments. Self-arms its own `/loop` — the user invokes once and walks away.

  • Ship issue

    semanticpixel/abc/plugins/abc/skills/ship-issue Skill

    0★ repo

    Linear · Drives a Linear issue (or list, or parent with sub-issues) from Backlog to Done through the implement → PR → address-review → merge loop. TRIGGER when the user says "/ship-issue TICKET-ID", asks to ship/land/drive/autoland a ticket, or wants Claude to take a Linear issue through review to merge. Also trigger when resuming work on a ticket with an open PR and pending reviewer comments. Supports GitHub + GitLab and multi-repo parent issues via `repo:` Linear labels. Self-arms its own `/loop` — the user invokes once and walks away.

  • Nebo devops cloud

    lifenewjob/nebo-claude-skills-public/skills/nebo-devops-cloud Skill

    0★ repo

    DEVOPS-CLOUD. Triggers: docker", "kubernetes", "CI/CD", "деплой", "AWS", "nginx", "systemd", "devops", "monitoring", "Helm

  • Nebo git workflow

    lifenewjob/nebo-claude-skills-public/skills/nebo-git-workflow Skill

    0★ repo

    GIT-WORKFLOW. Triggers: git commit, PR, code review, branch, worktree, issue triage

  • Content ops director

    PlevanTem/luban-skill/.claude/skills/content-ops-director Skill

    0★ repo

    Reviews B2B SaaS Content Operations Director-level decisions for cross-region content ops systems spanning 国内社媒 (小红书 / 知乎 / 视频号 / 抖音 / 公众号) and overseas (LinkedIn / TikTok / YouTube / Twitter / Substack / Reddit). Activates when the user is designing content strategy from scratch, ranking channel ROI, evaluating editorial calendar structure, diagnosing why content is not shipping pipeline, building founder-led / employee-led / 个人 IP / KOS programs, integrating AI into content workflow, or staffing 3-5 person content teams. Defaults to measurement-first, core-asset-fanout, and mechanism-over-platform stances. Does not handle single-piece content craft (copywriting, video editing, carousel design — defer to IC content marketer / designer), B2C consumer brand / MCN / 直播带货 content (defer to consumer-domain expert), MarTech tool implementation depth (defer to MarTech ops specialist), or under-50-person organizations where full-stack ops is over-engineered.

  • Game art director

    PlevanTem/luban-skill/.claude/skills/game-art-director Skill

    0★ repo

    Reviews and shapes 0→1 visual-定调期 decisions for game art direction — finding the style, defining visual DNA, shipping a v0.1 style guide, running the first concept reviews. Activates when the user is establishing a game's visual identity, writing or critiquing an art bible / style guide, doing concept-art critique, debating realism vs stylization, picking thematic keywords, or trying to escape the "Cult of Good Enough" trap. Does not handle scale-stage art ops (1→10 multi-team production lines), long-term IP maintenance (seasons, collaborations, merch derivatives), craft-level IC mentoring (specific Photoshop / ZBrush / Substance techniques — defer to craft mentor), or KV / trailer / store-page marketing design (defer to brand & marketing designer).

  • Cloudflare dns deploy

    iansteitz1-eng/aria-skills/cloudflare-dns-deploy Skill

    no license0★ repo

    Reconcile DNS records from a declared YAML catalog to Cloudflare via the API, and optionally run the companion nginx + certbot bootstrap for records pointing at your server. Idempotent. --dry-run by default, --apply hits the API, --server-setup also wires nginx + obtains Let's Encrypt cert. Use when the user says "deploy DNS", "add a subdomain", "stand up <X>.example.com", or before any subdomain launch.

  • Github repo deploy

    iansteitz1-eng/aria-skills/github-repo-deploy Skill

    no license0★ repo

    Reconcile a YAML catalog of GitHub repo metadata (description, homepage, topics) to the live GitHub account. Idempotent, --dry-run by default, --apply --prod for the live PATCH. Auth via `gh auth token` or GITHUB_TOKEN env. Refuses to change visibility (public/private) or default_branch without explicit override. Use when the user says "polish my repos", "update GitHub descriptions", "tag my repos for discoverability", "fix repo metadata", or before any campaign that drives traffic to GitHub. Single-command alternative to clicking through every repo's settings page.

  • Headless claude

    iansteitz1-eng/aria-skills/headless-claude Skill

    no license0★ repo

    Run the `claude` CLI fast, hook-free, and unattended for automation — wraps `claude -p` with --setting-sources project (skip your user hooks + heavy auto-memory, ~2s not ~15s), --permission-mode bypassPermissions (no interactive approval prompt that would block a script), and a neutral cwd. Uses your own plan, no API key. Use when the user says "run claude headless", "scriptable claude", "claude -p keeps hanging / prompting", "call claude from a cron/agent", or is automating Claude Code.

  • Marketplace publish

    iansteitz1-eng/aria-skills/marketplace-publish Skill

    no license0★ repo

    Unified marketplace publisher for VS Code Marketplace (via vsce), iOS App Store / TestFlight (via Expo EAS submit), and Google Play Console (via Expo EAS submit). Single command surface around publish.sh + submit.sh. Pre-flight validates credentials before doing anything destructive. --dry-run by default skips uploads. Use when the user says "publish the extension", "submit to App Store", "ship to Play Store", "marketplace publish", "release the vsix", "build and submit", or before any app-store push.

  • Solana deploy

    locallaunchsc-cloud/solana-dev-skills/solana-deploy Skill

    0★ repo

    Use this skill when the user wants to deploy or upgrade a Solana program from devnet to mainnet — verifiable builds, buffer accounts, priority fees, upgrade authority management, IDL upload, program close.

  • Editorial workflow tw

    richardvt/claude-skills-journalism-tw/journalism-core-tw/skills/editorial-workflow-tw Skill

    no license0★ repo

    台灣編輯部新聞流程與選題管理 (繁體中文/台灣專用版,對應 upstream editorial-workflow 的美國版)。涵蓋:選題追蹤、編輯部分工、版面排期、新聞 SOP、發稿前審核流程、責任歸屬、新進記者訓練。建置編輯部流程、選題會議、稿單管理、deadline 追蹤、編輯/記者交接時觸發。編輯主管、副總編、執行編輯、自由工作者管理多個媒體時必備。

  • Fact check workflow tw

    richardvt/claude-skills-journalism-tw/journalism-core-tw/skills/fact-check-workflow-tw Skill

    no license0★ repo

    台灣新聞事實查核工作流程 (繁體中文/台灣專用版,對應 upstream fact-check-workflow 的美國版)。涵蓋:主張提取與優先級、台灣主要資料來源 (政府開放資料、機關澄清專區、IFCN 認證查核機構)、台灣主要查核來源 (台灣事實查核中心、MyGoPen、Cofacts、蘭姆酒吐司) 與 LINE 訊息查證、證據蒐集與存檔、求證來源、評等量表 (6 級制)、更正流程、法律風險 (《刑法》§310 誹謗罪、《社會秩序維護法》§63 散布謠言)、常見台灣假訊息類別 (政治/兩岸/健康/食安/詐騙)、發稿前 checklist。涉及事實查核、查證、闢謠、求證、評等、發稿前審核時觸發。投入查核報導、調查報導、新聞編輯部、媒體素養教育之記者必備。

  • Ship security

    aksheyw/claude-code-ship-gate/plugins/ship-gate/skills/ship-security Skill

    0★ repo

    Ship Gate security gate, applies the distilled security checklist to the diff; optionally augments with /security-review.

  • Ship

    aksheyw/claude-code-ship-gate/plugins/ship-gate/skills/ship Skill

    0★ repo

    Run the ship-gate quality gates and push to the protected branch (usually main). Invoke when the user expresses intent to ship, release, or push to the main/protected branch (e.g. "ship it", "go ahead and ship", "sync with GitHub"). On an imperative command, auto-push when all gates pass; on a question or a "not yet", run the gates and report without pushing.

  • Ship

    kompiro/hane/skills/ship Skill

    0★ repo

    コミット済みの変更を PR 作成 → CI 確認 → クリーンアップまで進めるワークフロー。 start-dev スキルを使わずに開発した場合にも対応する。 Trigger when the user says: "ship", "ship it", "PRを作って", "PR作成", "プッシュしてPR", "出荷", "create PR", "push and PR", "submit PR", "マージまで", or similar phrases requesting to push, create a PR, or finish development.

  • Sdlc release validator

    mercedesperezcapilla-gif/claude-skills/skills/sdlc-release-validator Skill

    0★ repo

    Validates that a software change has met all required SDLC gates before or after release in a regulated financial services environment. Checks 14 gates — change record, design agreement, code review, developer testing, independent testing, environment consistency, UAT sign-off, bug management, go/no-go, post-release validation, exceptions and manual interventions, rollback plan, impact communication, and security review. Returns a gate-by-gate status report and a structured sign-off block ready for audit. Use before a release to check readiness, after to confirm completeness, or during a review to evidence what was done.

  • Agentic actions auditor

    bertbertov/claude-stack/skills/agentic-actions-auditor Skill

    0★ repo

    Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

    The same file is in 3 other repositories

  • Expo cicd workflows

    bertbertov/claude-stack/skills/expo-cicd-workflows Skill

    0★ repo

    Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.

    The same file is in 7 other repositories

  • Expo deployment

    bertbertov/claude-stack/skills/expo-deployment Skill

    0★ repo

    Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes

    The same file is in 7 other repositories

  • Git workflow

    bertbertov/claude-stack/skills/git-workflow Skill

    0★ repo

    Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.

    The same file is in 3 other repositories

  • N8n code javascript

    bertbertov/claude-stack/skills/n8n-code-javascript Skill

    0★ repo

    Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, choosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, API calls, format conversion, batch processing logic, or any custom JavaScript. Covers SplitInBatches loop patterns, cross-iteration data, pairedItem, and real-world production patterns.

    The same file is in 1 other repository

  • N8n code python

    bertbertov/claude-stack/skills/n8n-code-python Skill

    0★ repo

    Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes. Use this skill when the user specifically requests Python for an n8n Code node. Note — JavaScript is recommended for 95% of use cases — only use Python when the user explicitly prefers it or the task requires Python-specific standard library capabilities (regex, hashlib, statistics).

    The same file is in 2 other repositories

  • N8n expression syntax

    bertbertov/claude-stack/skills/n8n-expression-syntax Skill

    0★ repo

    Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from previous nodes — expressions are how n8n passes data between nodes, and getting the syntax wrong is the most common source of workflow errors.

    The same file is in 2 other repositories

  • N8n mcp tools expert

    bertbertov/claude-stack/skills/n8n-mcp-tools-expert Skill

    0★ repo

    Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns. IMPORTANT — Always consult this skill before calling any n8n-mcp tool — it prevents common mistakes like wrong nodeType formats, incorrect parameter structures, and inefficient tool usage. If the user mentions n8n, workflows, nodes, or automation and you have n8n MCP tools available, use this skill first.

  • N8n node configuration

    bertbertov/claude-stack/skills/n8n-node-configuration Skill

    0★ repo

    Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates.

    The same file is in 2 other repositories

  • N8n validation expert

    bertbertov/claude-stack/skills/n8n-validation-expert Skill

    0★ repo

    Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities. Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings — it knows which warnings are false positives and which errors need real fixes.

    The same file is in 2 other repositories

  • N8n workflow patterns

    bertbertov/claude-stack/skills/n8n-workflow-patterns Skill

    0★ repo

    Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled tasks. Always consult this skill when the user asks to create, build, or design an n8n workflow, automate a process, or connect services — even if they don't explicitly mention 'patterns'. Covers webhook, API, database, AI, batch processing, and scheduled automation architectures.

    The same file is in 2 other repositories

  • Publish models

    bertbertov/claude-stack/skills/publish-models Skill

    0★ repo

    Push and publish custom AI models to Replicate, and set up CI/CD for releasing new model versions safely. Use when running cog push, deploying a model to Replicate, releasing a new version, validating a model with cog-safe-push before publishing, configuring a Replicate deployment, setting up GitHub Actions for model releases, or porting a community model to an official one. Trigger on phrases like "push a model to Replicate", "publish a model", "deploy a model", "release a new version", "cog push", "cog-safe-push", "model CI", "r8.im", or "schema compatibility", and when referencing github.com/replicate/cog-safe-push or github.com/replicate/model-ci-template. Covers cog push, the full cog-safe-push config (test cases, fuzz, deployment, official_model), GitHub Actions patterns, multi-model matrix pushes, and post-publish monitoring. Assumes you already have a working Cog project; see build-models if you need to package one first.

  • React native apps

    bertbertov/claude-stack/skills/react-native-apps Skill

    0★ repo

    Complete skill for building, debugging, and shipping React Native / Expo apps in 2025-2026. Use when the user is building a mobile app, starting a new Expo project, debugging Expo Go crashes, setting up EAS builds, submitting to Google Play / App Store, writing animation patterns, or asking about mobile architecture decisions. Distilled from production Expo SDK 54 apps, official docs, Reddit r/reactnative hot threads, GitHub issues on expo/expo and facebook/react-native, and teardowns of shipped apps (Elirox, Instamobile templates). Covers 13 gotchas, 13 UX patterns, full deployment pipeline, animation stack, and production architecture boilerplate.

  • Runpod

    bertbertov/claude-stack/skills/runpod Skill

    0★ repo

    Cloud GPU processing via RunPod serverless. Use when setting up RunPod endpoints, deploying Docker images, managing GPU resources, troubleshooting endpoint issues, or understanding costs. Covers all 5 toolkit images (qwen-edit, realesrgan, propainter, sadtalker, qwen3-tts).

  • Tdd workflow

    bertbertov/claude-stack/skills/tdd-workflow Skill

    0★ repo

    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

    The same file is in 8 other repositories

  • Pre mortem

    marsloting/product-thinking-pack/skills/pre-mortem Skill

    0★ repo

    Run pre-mortem (Klein) and FMEA-style failure-mode analysis BEFORE shipping a plan, feature, launch, campaign, or strategic decision. Use whenever 用户 says "这个方案有什么风险" / "上线前最后过一遍" / "万一失败了什么原因" / "risk register" / "what could go wrong" / "事先复盘" / "失败推演". Forces "imagine it failed in 6 months — write the autopsy" perspective shift, distinguishes pre-mortem (causes) from FMEA (severity × probability × detectability), produces concrete risk register with mitigation owner. Stops optimism bias, surfaces blind spots before they ship. Self-contained methodology — no external docs required.

  • Leadup deploy checker

    leadupofficial/leadup-claude-skills/leadup-deploy-checker Skill

    0★ repo

    Check whether a LeadUp project is ready to deploy to leadup-server / Coolify. Verifies Docker build, env variable coverage, ports, Coolify config, GitHub branch, domain/subdomain, migrations, and a rollback plan, then outputs a READY / NOT READY verdict. Use when the user says "prepare deploy", "deploy checker", "make Docker work", "Coolify deploy", "leadup-server deploy", or "production ready".