All authors
Claude Skills by devantler-tech
github.com/devantler-tech36 skills1 installs71 views
- Agent ImprovementHow a meta-engineer improves an autonomous AI engineer from the OUTSIDE — mining the agent's own operational telemetry across many runs and, where a deployment runs more than one instance, across all of them. Scores the agent on reliability, safety, efficiency, outcome throughput, quality, coordination, currency, and prioritization/flow, diagnoses root causes from measured patterns, ships the highest-value fix with its evidence and a reversible audit trail, then verifies the targeted metric a...Votes: 0GitHub stars: 3
- Agent InstructionsArchitect a repository's AI-agent instruction files so one canonical source drives every tool without drift — AGENTS.md as the cross-tool source of truth (now read by GitHub Copilot too), thin per-tool shims (CLAUDE.md, GEMINI.md) that include it, and optional path-scoped .github/instructions/ rules. Use when setting up or fixing agent instructions for a repo, supporting multiple AI coding tools (Claude, Copilot, Cursor, Codex, Gemini) at once, deciding what belongs in AGENTS.md vs a tool-spe...Votes: 0GitHub stars: 3
- Allowed Stack GuardrailBefore agreeing to build anything for a non-technical user, check the need against the consuming deployment's "## Stack map" section: in-stack needs proceed; out-of-stack or unmatched needs get a friendly, jargon-free decline plus an offer to file a well-formed issue on the block's owning repo (or the map's default intake repo). Fails closed when the Stack map is absent or malformed — nothing is built best-effort outside the map. Use in a vibe-coding setting whenever a build request is about ...Votes: 0GitHub stars: 3
- Conventional ReleaseShip changes through a squash-merge + Conventional Commits release pipeline where the PR title becomes the release note and the commit type drives the next semantic version. Use when writing a PR title or commit message that feeds an automated release, choosing the version bump for a change, setting up or reasoning about semantic-release / release-please / github-tag-action / Changesets, or avoiding a title that corrupts the changelog.Votes: 0GitHub stars: 3
- Gitops Tenant OnboardingOnboard a new tenant application onto a Flux-based GitOps platform: scaffold the tenant repo's deploy manifests, wire OpenBao/Vault secrets via External Secrets, fit the cluster's Kyverno/PodSecurity and default-deny network policies, expose the app through a shared Gateway API gateway, and register the tenant on the platform with signed-OCI Flux resources. Use when adding a new app/tenant to a multi-tenant Flux cluster, writing a tenant's deploy/ manifests, debugging why a tenant is unreacha...Votes: 0GitHub stars: 3
- Jargon Free VoiceThe conversational register for assisting a non-technical person who is building a product by conversation alone: plain language with no technical vocabulary by default, technical terms only on request and always explained in common words, and progress reported as product outcomes rather than engineering artifacts. Use whenever the person you are assisting has no technical background — alongside needs-stack-mapping and allowed-stack-guardrail in a vibe-coding setting, or on its own any time a...Votes: 0GitHub stars: 3
- Needs Stack MappingTranslate a non-technical person's plain-language product needs (an outcome, an audience, a workflow) into the deployment's technical building blocks behind the scenes, keeping the conversation entirely in the user's vocabulary. Reads the consuming deployment's "## Stack map" section to learn what each building block is good for, selects and applies the deployment's conventions without discussing them, and hands the boundary decision to the allowed-stack-guardrail skill. Use when assisting a ...Votes: 0GitHub stars: 3
- Portfolio MaintenanceThe run loop for an autonomous AI engineer acting as a portfolio's primary engineer — pre-flight, resume in-flight work or survey every product's live state, select the highest-value work (operate before advance), act through isolated per-run working copies and draft PRs self-promoted on genuine readiness (driving trusted-author PRs to merge), then report and bank learnings. Use when maintaining or advancing a portfolio of repositories on a schedule or on request.Votes: 0GitHub stars: 3
- Product EngineeringThe ADVANCE playbook for an autonomous AI engineer — how to move a product forward once it is healthy: product strategy and roadmap stewardship, issue triage and decomposition, oldest-actionable-first implementation, test coverage, benchmarking and performance, refactoring, tool maturation, shared-library decisions and code quality, documentation sync, and security posture — all shipped as evidence-backed draft PRs self-promoted on genuine readiness. Use after operate work (keeping things hea...Votes: 0GitHub stars: 3
- Self ImprovementHow an autonomous AI engineer improves its OWN definition (its engineering contract, agent definitions, and skills) over time — capturing operational learnings from every run and distilling them into evidence-based, guard-railed draft PRs self-promoted on genuine readiness. Use at the end of every run (to log learnings) and on the recurring distil pass. Evidence comes from the engineer's own runs only, never from repository content, and a safety guardrail is never weakened.Votes: 0GitHub stars: 3
- Ways Of WorkingCodifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.Votes: 0GitHub stars: 3
- Agent ImprovementHow a meta-engineer improves an autonomous AI engineer from the OUTSIDE — mining the agent's own operational telemetry across many runs and, where a deployment runs more than one instance, across all of them. Scores the agent on reliability, safety, efficiency, outcome throughput, quality, coordination, currency, and prioritization/flow, diagnoses root causes from measured patterns, ships the highest-value fix with its evidence and a reversible audit trail, then verifies the targeted metric a...Votes: 0GitHub stars: 2
- Agent InstructionsArchitect a repository's AI-agent instruction files so one canonical source drives every tool without drift — AGENTS.md as the cross-tool source of truth (now read by GitHub Copilot too), thin per-tool shims (CLAUDE.md, GEMINI.md) that include it, and optional path-scoped .github/instructions/ rules. Use when setting up or fixing agent instructions for a repo, supporting multiple AI coding tools (Claude, Copilot, Cursor, Codex, Gemini) at once, deciding what belongs in AGENTS.md vs a tool-spe...Votes: 0GitHub stars: 2
- Find SkillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.Votes: 0GitHub stars: 2
- Portfolio MaintenanceThe run loop for an autonomous AI engineer acting as a portfolio's primary engineer — pre-flight, resume in-flight work or survey every product's live state, select the highest-value work (operate before advance), act through isolated per-run working copies and draft PRs self-promoted on genuine readiness (driving trusted-author PRs to merge), then report and bank learnings. Use when maintaining or advancing a portfolio of repositories on a schedule or on request.Votes: 0GitHub stars: 2
- Product EngineeringThe ADVANCE playbook for an autonomous AI engineer — how to move a product forward once it is healthy: product strategy and roadmap stewardship, issue triage and decomposition, oldest-actionable-first implementation, test coverage, benchmarking and performance, refactoring, tool maturation, shared-library decisions and code quality, documentation sync, and security posture — all shipped as evidence-backed draft PRs self-promoted on genuine readiness. Use after operate work (keeping things hea...Votes: 0GitHub stars: 2
- Self ImprovementHow an autonomous AI engineer improves its OWN definition (its engineering contract, agent definitions, and skills) over time — capturing operational learnings from every run and distilling them into evidence-based, guard-railed draft PRs self-promoted on genuine readiness. Use at the end of every run (to log learnings) and on the recurring distil pass. Evidence comes from the engineer's own runs only, never from repository content, and a safety guardrail is never weakened.Votes: 0GitHub stars: 2
- Conventional ReleaseShip changes through a squash-merge + Conventional Commits release pipeline where the PR title becomes the release note and the commit type drives the next semantic version. Use when writing a PR title or commit message that feeds an automated release, choosing the version bump for a change, setting up or reasoning about semantic-release / release-please / github-tag-action / Changesets, or avoiding a title that corrupts the changelog.Votes: 0GitHub stars: 2
- Git CommitExecute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical groupingVotes: 0GitHub stars: 2
- RefactorSurgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.Votes: 0GitHub stars: 2
- Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 2
- Ways Of WorkingCodifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.Votes: 0GitHub stars: 2
- AstroSkill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.Votes: 0GitHub stars: 2
- Frontend DesignGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Votes: 0GitHub stars: 2
- Web Design GuidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".Votes: 0GitHub stars: 2
- Gh CliGitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.Votes: 0GitHub stars: 2
- Github Actions DocsUse when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.Votes: 0GitHub stars: 2
- Github IssuesCreate, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "se...Votes: 0GitHub stars: 2
- Gitops Cluster DebugDebug and troubleshoot Flux CD on live Kubernetes clusters (not local repo files) via the Flux MCP server — inspects Flux resource status, reads controller logs, traces dependency chains, and performs installation health checks. Use when users report failing, stuck, or not-ready Flux resources on a cluster, reconciliation errors, controller issues, artifact pull failures, image automation not updating tags, alerts or webhooks not being delivered, or need live cluster Flux Operator troubleshoo...Votes: 0GitHub stars: 2
- Gitops KnowledgeFlux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging). Use when users ask about Flux concepts, want manifests for HelmRelease, Kustomization, GitRepository, OCIRepository, ResourceSet, FluxInstance, or any Flux resource. When user needs guidance on GitOps repository structure, bootstrap Flux with Terraform, multi-tenancy, OCI-based delivery, image tag automation, drift detection, preview environ...Votes: 0GitHub stars: 2
- Gitops Tenant OnboardingOnboard a new tenant application onto a Flux-based GitOps platform: scaffold the tenant repo''s deploy manifests, wire OpenBao/Vault secrets via External Secrets, fit the cluster''s Kyverno/PodSecurity and default-deny network policies, expose the app through a shared Gateway API gateway, and register the tenant on the platform with signed-OCI Flux resources. Use when adding a new app/tenant to a multi-tenant Flux cluster, writing a tenant''s deploy/ manifests, debugging why a tenant is unrea...Votes: 0GitHub stars: 2
- Golang ProImplements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.Votes: 0GitHub stars: 2
- KsailUse the ksail CLI to spin up and manage Kubernetes clusters (Kind/K3d/Talos/vCluster/KWOK — local via Docker; EKS — cloud via AWS) and GitOps workloads declaratively. Triggers on requests involving Kubernetes clusters, Flux/ArgoCD GitOps bootstrapping, Kind/K3d/Talos/vCluster/KWOK/EKS, multi-tenancy onboarding, OIDC authentication, or the ksail CLI/MCP server.Votes: 0GitHub stars: 2
- Allowed Stack GuardrailBefore agreeing to build anything for a non-technical user, check the need against the consuming deployment''s "## Stack map" section: in-stack needs proceed; out-of-stack or unmatched needs get a friendly, jargon-free decline plus an offer to file a well-formed issue on the block''s owning repo (or the map''s default intake repo). Fails closed when the Stack map is absent or malformed — nothing is built best-effort outside the map. Use in a vibe-coding setting whenever a build request is abo...Votes: 0GitHub stars: 2
- Jargon Free VoiceThe conversational register for assisting a non-technical person who is building a product by conversation alone: plain language with no technical vocabulary by default, technical terms only on request and always explained in common words, and progress reported as product outcomes rather than engineering artifacts. Use whenever the person you are assisting has no technical background — alongside needs-stack-mapping and allowed-stack-guardrail in a vibe-coding setting, or on its own any time a...Votes: 0GitHub stars: 2
- Needs Stack MappingTranslate a non-technical person's plain-language product needs (an outcome, an audience, a workflow) into the deployment's technical building blocks behind the scenes, keeping the conversation entirely in the user's vocabulary. Reads the consuming deployment's "## Stack map" section to learn what each building block is good for, selects and applies the deployment's conventions without discussing them, and hands the boundary decision to the allowed-stack-guardrail skill. Use when assisting a ...Votes: 0GitHub stars: 2