.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/nixopus/nixopus
home/skills/nixopus/nixopus
nixopus avatar

nixopus/nixopus

41 skills

View on GitHub
$npx skills add nixopus/nixopus
SkillInstalls
api-catalogReference for all Nixopus API operations callable via nixopus_api(method, path, body)—caddyfile-generationGenerate Caddyfile configurations for static sites and reverse proxies — SPA fallback routing, cache headers, compression, redirects, and error pages.—compose-setupGenerate docker-compose.yml for multi-service setups including databases, caches, and service dependencies.—container-resource-tuningSize container memory and CPU limits, diagnose OOM kills and CPU throttling, and recommend resource adjustments by ecosystem.—cpp-deployBuild and deploy C/C++ applications — CMake, Meson, Ninja, and Dockerfile patterns.—database-migrationRun database migrations safely during deployment — framework-specific commands, pre-deploy vs post-deploy timing, health gates, and rollback strategies.—deno-deployBuild and deploy Deno applications — version detection, dependency caching, and Dockerfile patterns.—deploy-delegationSub-agent routing table — which agent handles diagnostics, machine health, infrastructure, GitHub, billing, and notifications.—deploy-flowFull deploy pipeline — source detection, hints-driven analysis, project creation, deployment monitoring, and live URL delivery.—deployment-analysisAnalyze a repository to determine ecosystem, deployment targets, ports, build commands, and monorepo structure.—diagnostic-workflowLayer-by-layer diagnostic workflow for application and container issues — deployment logs, container state, HTTP probes.—dockerfile-generationGenerate production-ready multi-stage Dockerfiles per ecosystem with best practices.—dockerignore-generationGenerate ecosystem-specific .dockerignore files to reduce build context size and prevent secret leaks.—domain-attachmentDomain setup for applications. Preferred path is passing domains at creation time via createProject.—domain-tls-routingDiagnose domain resolution, TLS certificate provisioning, and reverse proxy routing issues.—dotnet-deployBuild and deploy .NET applications — ASP.NET Core, version detection, self-contained builds, and Dockerfile patterns.—elixir-deployBuild and deploy Elixir and Phoenix applications — version detection, mix releases, and Dockerfile patterns.—env-detectionDetect required environment variables from source code, config files, and .env examples.—failure-diagnosisDiagnose deployment failures, container crashes, and networking issues using structured pattern matching on logs and container state.—github-onboardingGuide users through connecting GitHub to Nixopus when no GitHub connector exists.—github-workflowFix-via-PR workflow, file operations, connector resolution, and GitHub safety rules.—gleam-deployBuild and deploy Gleam applications — erlang-shipment, version detection, and Dockerfile patterns.—go-deployBuild and deploy Go applications — version detection, static binaries, CGO, workspaces, and Dockerfile patterns.—incident-responseStructured incident response workflow — severity classification, diagnosis delegation, auto-fix decisions, notification, and post-incident review.—java-deployBuild and deploy Java applications — Maven, Gradle, Spring Boot, version detection, and Dockerfile patterns.—machine-opsMachine-level diagnostic layers, lifecycle management (restart/pause/resume), metrics analysis, and backup operations.—mcp-integrationsMCP server discovery, tool invocation, and provider catalog integration.—monorepo-strategyDeploy multi-service monorepo applications — service discovery, dependency ordering, shared build contexts, selective deployment, and compose generation.—nixopus-docsLook up Nixopus platform documentation at runtime. Use when the user asks about Nixopus features, configuration, concepts, self-hosting, API reference, guides,…—node-deployBuild and deploy Node.js applications — version detection, package managers, framework-specific builds, monorepo support, and Dockerfile patterns.—onboardingProactive welcome flow for new Nixopus users. Triggered by the frontend __ONBOARD__ signal when a user has no GitHub connectors and no deployed applications.—php-deployBuild and deploy PHP applications — Composer, Laravel, Symfony, FrankenPHP, PHP-FPM, and Dockerfile patterns.—post-deploy-verificationVerify a deployment is healthy after it completes — HTTP probes, healthcheck endpoints, container stability, log scanning, and port alignment.—pre-deploy-checklistValidate deployment readiness before triggering a build — check Dockerfile, ports, env vars, healthchecks, and resource config.—python-deployBuild and deploy Python applications — uv, poetry, pdm, pipenv, pip, framework detection, and Dockerfile patterns.—rollback-strategyGuide rollback decisions after failed deployments — when to rollback vs retry, verification after rollback, and state preservation.—ruby-deployBuild and deploy Ruby applications — Bundler, Rails, Rack, asset pipeline, bootsnap, and Dockerfile patterns.—rust-deployBuild and deploy Rust applications — version detection, release binaries, cargo-chef, and Dockerfile patterns.—self-healSelf-healing loop for failed deployments — diagnose, fix, redeploy up to 3 attempts, then escalate or rollback.—shell-deployDeploy shell script applications — interpreter detection, setup scripts, and Dockerfile patterns.—static-deployDeploy static file sites — Caddy/nginx serving, Staticfile config, and Dockerfile patterns.—