use-cdkd

Build cdkd and generate absolute-path CLI commands for CDK projects.

97|4|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/go-to-k/cdkd --skill use-cdkd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-cdkd
Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/use-cdkd
Command: npx skills add https://github.com/go-to-k/cdkd --skill use-cdkd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build cdkd in your environment and generate ready-to-use commands for other CDK projects, enabling rapid adoption and sharing of CLI workflows.

Core Features & Use Cases

  • Build the cdkd binary locally for test and deployment workflows.
  • Output absolute-path commands ready for copy-paste into other CDK projects.
  • Use cases include onboarding teams, CI pipelines, and multi-repo CDK automation.

Quick Start

Build the project and copy the absolute path to the built CLI, then paste it into new CDK projects to run the provided commands.

Frequently Asked Questions about use-cdkd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a CDK CLI tool and generate ready-to-use commands for multiple projects?

You can build the cdkd project using a Node-based build process that outputs a runnable CLI at dist/cli.js, then copy the absolute path to paste ready-to-use commands into other CDK projects.

Does the cdkd build process require pnpm to run the generated CLI?

The cdkd build process does not strictly require pnpm to run the generated CLI, as it supports direct node invocations, but it also supports global pnpm linking for streamlined local development.

How do I automate cdkd command generation for CI pipelines?

To automate cdkd command generation for CI pipelines, run the Node-based build process to output the CLI at dist/cli.js, then use the absolute-path commands for deployment workflows across multiple CDK repositories.

What is the best way to share CDK automation workflows across different repositories?

The best way to share CDK automation workflows is building cdkd locally to generate absolute-path commands that can be copy-pasted into different repositories, enabling rapid onboarding and consistent CLI execution.

Why use absolute-path commands when integrating cdkd into a new CDK project?

Using absolute-path commands when integrating cdkd allows you to directly execute the built CLI from dist/cli.js without complex path resolutions, ensuring immediate and reliable access to the provided CDK automation commands.

Can I use cdkd for onboarding teams to multi-repo CDK environments?

Yes, you can use cdkd for onboarding teams to multi-repo CDK environments by building the binary locally and sharing the generated absolute-path commands for rapid adoption of CLI workflows.