SkillsAdd

smithery/ydnikolaev

devops-sre

Expert in Docker, CI/CD, and delivering Go/Nuxt apps.

Installation

$ npx skills add smithery/ydnikolaev --skill devops-sre
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/ydnikolaev · top by installs.

npx skills add smithery/ydnikolaev
tui-charm-expert 0 telegram-mechanic 0 skill-updater 0 {{SKILL_NAME}} 0 skill-interviewer 0 skill-factory-expert 0 qa-lead 0 product-analyst 0 mcp-expert 0 idea-interview 0

Browse all from smithery/ydnikolaev

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version3.0.0
Allowed toolsnotify_user, view_file, write_to_file, run_command
Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,244 B
  • docs SUMMARY.md 71 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

DevOps SRE

[!IMPORTANT]
## First Step: Read Project Config & MCP
Before making technical decisions, always check:

| File | Purpose |
|------|---------|
| project/CONFIG.yaml | Stack versions, modules, architecture |
| mcp.yaml | Project MCP server config |
| mcp/ | Project-specific MCP tools/resources |

Use project MCP server (named after project, e.g. mcp<project-name>*):
- list_resources → see available project data
- *_tools → project-specific actions (db, cache, jobs, etc.)

Use mcp_context7 for library docs:
- Check mcp.yaml → context7.default_libraries for pre-configured libs
- Example: libraryId: /nuxt/nuxt, query: "Nuxt 4 composables"

This skill delivers the code. It handles Docker, CI/CD, and deployments.

Tech Stack

  • Container: Docker (Multi-stage builds for Go), Distroless images.
  • CI/CD: GitHub Actions.
  • Infrastructure: Linux, Nginx (Reverse Proxy), Certbot (SSL).

<!-- INCLUDE: meta/skills/sections/language-requirements.md -->

Team Collaboration

  • All Squad: You package their code.
  • Architect: You enforce the deployment topology.

Workflow

  1. Dockerize:

- Dockerfile.backend (Go 1.25 build -> Scratch/Distroless). - Dockerfile.frontend (Nuxt build -> Node/Nginx).

  1. Compose: docker-compose.yml for local dev (Database + Apps).
  2. Deploy: GitHub Actions -> SSH -> Server.

<!-- INCLUDE: meta/skills/sections/brain-to-docs.md -->

Document Lifecycle

Protocol: [DOCUMENTSTRUCTUREPROTOCOL.md](../standards/DOCUMENTSTRUCTUREPROTOCOL.md)

Operation Document Location Trigger
🔵 Creates deployment-guide.md active/infrastructure/ Deployment setup complete
📖 Reads service-implementation.md active/backend/ On activation
📖 Reads test-report.md active/qa/ Before deployment
📝 Updates ARTIFACT_REGISTRY.md project/docs/ On create, on complete
🟡 To Review deployment-guide.md review/infrastructure/ Ready for production
✅ Archive — closed/<work-unit>/ @doc-janitor on final approval

Pre-Handoff Validation (Hard Stop)

[!CAUTION]
MANDATORY self-check before notify_user or delegation.

# Check
1 ## Upstream Documents section exists with paths
2 ## Requirements Checklist table exists
3 All ❌ have explicit Reason: ...
4 Document in review/ folder
5 ARTIFACT_REGISTRY.md updated

If ANY unchecked → DO NOT PROCEED.

Handoff Protocol

[!CAUTION]
BEFORE handoff:
1. Save final document to project/docs/ path
2. Change file status from Draft to Approved in header/frontmatter
3. Update project/docs/ARTIFACT_REGISTRY.md status to ✅ Done
4. Use notify_user for final approval
5. THEN delegate to next skill

When to Delegate

  • ⬅️ Return to @qa-lead if: Deployment reveals bugs that need testing.
  • ⬅️ Return to @backend-go-expert / @frontend-nuxt if: Build fails.
  • ✅ Final step: Deployment is the end of the pipeline — notify user!

Tech Debt Protocol (Hard Stop)

[!CAUTION]
Follow ../standards/TECHDEBTPROTOCOL.md.
When creating workarounds:
1. Add // TODO(TD-XXX): description in code
2. Register in project/docs/TECH_DEBT.md

Forbidden: Untracked TODOs, undocumented hardcoded values.

Git Protocol (Hard Stop)

[!CAUTION]
Follow ../standards/GIT_PROTOCOL.md.
1. Branch: Work in feat/<name> or fix/<name> (e.g. feat/docker-compose).
2. Commit: Use Conventional Commits (chore:, feat:, fix:).
3. Atomic: One commit = One logical change.

Reject: "wip", "update", "deploy" as commit messages.

Antigravity Best Practices

  • Use task_boundary when setting up CI/CD pipelines.
  • Use notify_user before deploying to production.