Centralize shared scripts and templates for My Kit workflow automation.
npx skills add https://github.com/mayknxyz/my-kit --skill mk
Please help me install this Agent Skill. Skill: mk Source: https://github.com/mayknxyz/my-kit/tree/main/kit/.claude/skills/mk Command: npx skills add https://github.com/mayknxyz/my-kit --skill mk
Centralizes My Kit's core infrastructure so other skills can share a consistent set of scripts, templates, and utilities without duplicating effort.
Use this skill as a reference container to explore and reuse its scripts and templates for your own mk-based skills.
High-intent search queries and answers about installing and using this skill.
Centralizing workflow automation scripts for Claude Code requires a shared infrastructure container to manage reusable bash utilities and templates. This standardizes path conventions like the $HOME/.claude structure, ensuring global accessibility and eliminating duplicated effort across skills.
Infrastructure workflow automation scripts require CLI dependencies including git, gh, jq, and bun to orchestrate tasks. Additional utilities like gitleaks, markdownlint, lychee, and linkinator handle security validation and markdown link checking.
Yes, bash scripts can automate git operations and security checks. Dedicated scripts like git-ops.sh handle branch management and git workflows, while security.sh integrates gitleaks to scan for sensitive data exposure during the automation process.
Available templates for spec, plan, and task documentation include reference formats for spec.md, plan.md, and tasks.md. An agent-context formatting template is also provided under references/templates to ensure consistent documentation structure across projects.
To validate markdown and check links in automated workflows, use markdownlint-cli2 for syntax enforcement and lychee or linkinator for link verification. These tools integrate into bash validation scripts to maintain documentation quality during automation.
Yes, setting up new feature workflows requires prerequisite checks. A dedicated check-prerequisites.sh script verifies that all required CLI tools and environment configurations are present before create-new-feature.sh initiates the feature setup process.
atournayreVerify gh CLI, jq, and git availability before automated workflows.
Marwan78888Dispatch plan tasks to fresh subagents with two-stage reviews.
tnezInstall a Git pre-commit hook that lints staged Markdown files with markdownlint-cli2.
garochee33Design automated CI/CD pipelines with GitHub Actions, Docker, and Terraform.
