krds-license

Verify and insert KRDS copyright attribution blocks in project files.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/JiminLee-way/Awsome-KRDS-KoreaDesignSystem --skill krds-license
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: krds-license
Source: https://github.com/JiminLee-way/Awsome-KRDS-KoreaDesignSystem/tree/main/plugins/krds/skills/krds-license
Command: npx skills add https://github.com/JiminLee-way/Awsome-KRDS-KoreaDesignSystem --skill krds-license

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The KRDS licensing workflow requires explicit copyright attribution and proper license text before deployment. This skill verifies presence of the required attribution block and can insert missing wording to ensure compliance across projects.

Core Features & Use Cases

  • Verify the mandatory attribution block is present in the codebase and documentation.
  • Check for the KRDS homepage link and 공공누리-type indicator.
  • Automatically insert the required attribution text in README, LICENSE, or related files as part of the release workflow.

Quick Start

Verify your project for KRDS attribution and insert the required public license text before deployment.

Frequently Asked Questions about krds-license

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

FAQPage Schema
How do I verify KRDS copyright attribution compliance before deployment?

Verify KRDS copyright attribution by checking for the mandatory attribution block text, KRDS homepage link, and 공공누리 type indicator across web, open-source, and npm package contexts before deployment.

Can I automatically insert missing KRDS license text into my README?

Yes, you can automatically insert missing KRDS license text into README, LICENSE, or related files to ensure proper copyright attribution and compliance as part of your release workflow.

What is the mandatory attribution block required for 공공누리 type KRDS projects?

The mandatory attribution block for 공공누리 type KRDS projects requires specific copyright attribution text, a KRDS homepage link, and the 공공누리 type indicator to ensure proper license compliance.

When do I need to check copyright attribution for KRDS-based projects?

Check copyright attribution for KRDS-based projects during deployment, commit, or publishing workflows to verify the required attribution block and 공공누리 license type are present.

Does the KRDS license verification work for npm packages and open-source repositories?

Yes, KRDS license verification works across web, open-source, and npm package contexts, checking for the mandatory attribution block, KRDS homepage link, and 공공누리 type indicator in each environment.

What happens if my project is missing the KRDS homepage link or 공공누리 indicator?

If your project is missing the KRDS homepage link or 공공누리 indicator, the verification identifies the gap and can automatically insert the required attribution text into your documentation files.