개발 스킬

Turn a recurring task into a reusable Open-Science Skill, or revise an existing one. Guide package creation, optional testing, improvements to when the Skill activates, and publication after the user reviews and accepts the draft.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning recurring tasks into reusable Skills
• Revising an existing Skill's instructions and files
• Evaluating outputs with realistic test prompts

Manage Python and R packages for notebook work. Resolve missing-package errors, check installed versions, install into the selected runtime, and restart the kernel when needed, with guidance on using separate environments for different dependency requirements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resolve missing-package errors in a notebook
• Check installed package versions
• Separate project dependencies into a named environment

Delegate a focused coding, research, review, or verification task to a separate DevSpace agent. Choose an available worker, provide a self-contained brief, inspect or wait for results, and continue related work with the same agent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Requesting an independent correctness or security review
• Investigating a bounded part of a codebase
• Delegating an isolated change with clear acceptance criteria

Review changes to a multilingual source code parser, focusing on whether relationships between code elements are correct. Check consistency across languages and verify that test examples reproduce the issue and actually validate the fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking constructor call and instantiation relationships
• Reviewing name resolution and scope handling
• Checking whether a parser fix applies to other languages

Investigate past agent runs using recorded tool results, commands, and file changes. Distinguish observed events from inferred causes, replay recorded decisions, or compare models from the same checkpoint to examine failures and alternative outcomes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing why a file was deleted or overwritten
• Finding the step that broke a build
• Replaying a recorded failure

Diagnose missing language features in Kode by checking LSP, the protocol connecting code tools to language servers. Update plugin configuration, confirm servers are recognized, and test an operation such as jumping to a definition.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Diagnosing missing LSP results in Kode
• Adding a language server through a plugin
• Reviewing a plugin's language server configuration

Build MCP servers, which connect AI agents to external services, using TypeScript or Python. Plan API access, design understandable tools and structured responses, implement authentication and error handling, and check behavior with the intended client.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building an MCP server for an external service
• Designing tool names, inputs, and responses for agents
• Implementing an MCP server in TypeScript or Python

Review SKILL.md files and their supporting resources using eight quality dimensions. Get a score out of 120, evidence for each assessment, and prioritized suggestions to improve specialized knowledge, activation descriptions, organization, and practical instructions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a skill before sharing it
• Improve descriptions that fail to trigger skill use
• Find redundant explanations in SKILL.md

Guide an AI agent through feature development, bug fixes, and refactoring with clear requirements, explained design choices, and small, tested changes. Keep human decisions central while making progress and verification results visible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding features to an existing project
• Tracing a bug to its root cause
• Refactoring code with tests in place

Configure Kode features by describing the changes you want. The skill inspects settings, adjusts status displays, response styles, and plugins, and verifies changes through settings checks and small practical operations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up or fixing the Kode status display
• Enabling TypeScript language support through plugins
• Changing the response style for a project

Turn specialized knowledge and repeatable workflows into an Agent Skill. Work through concrete usage examples, write SKILL.md, organize reusable scripts and resources, and validate the package before producing a distributable .skill file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn recurring work into a reusable skill
• Package internal knowledge and API instructions
• Revise an existing skill after real use

Build and update Kiln screens using shared interface components and established styles. The skill guides component planning, comparison with reference screens, automated rule checks, and a review handoff containing evidence of consistency and any justified exceptions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a Kiln screen using shared components
• Aligning forms and dialogs with established styles
• Checking Svelte changes for interface rule violations

Find documentation and agent instructions made outdated by a branch’s code changes. Update affected paths, commands, settings, and behavior descriptions in place, then commit the documentation fixes alongside the code in the same pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update documentation before opening a pull request
• Review documentation before pushing more commits to an open pull request
• Fix references after renaming scripts or public functions

Add AI models to Kiln or find available models missing from its list. The skill checks provider model identifiers and capabilities, updates model settings, runs tests against real APIs, and drafts a Discord announcement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a newly released model to Kiln
• Finding available models missing from Kiln
• Checking provider support for recently added models

Prepare Kiln pull requests with clear explanations of the changes, checks, and merge dependencies. Preserve sections reserved for human decisions, keep descriptions current after updates, and handle review comments and automated check failures with user consent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a pull request for human review
• Rewrite a pull request description
• Update the description after pushing changes

Apply Kiln’s coding rules when editing or reviewing Python, TypeScript, and Svelte. The skill combines area-specific guidance with a script that checks changed lines, plus manual checks for architecture, configuration handling, shared state, and asynchronous operations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking coding rules before changing Kiln
• Checking uncommitted changes for convention violations
• Reviewing a branch or pull request against shared rules

Build and extend JavaScript or TypeScript apps with TinyBase, keeping active data in the app runtime. The skill guides project generation, UI connections, data storage, and synchronization, with checks for reloads, two-client updates, and reconnection.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generate a new TinyBase application
• Connect data schemas and UI components
• Keep saved data available after a reload

Review a coding session to identify improvements to the agent’s working environment. Get prioritized suggestions for finding files, strengthening automated checks, clarifying guidance, reducing costly tool calls, and accessing missing information.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing why a coding agent struggled
• Finding gaps in automated checks
• Simplifying agent instructions

Set up dependency-cruiser in a TypeScript repository to enforce package boundaries: outside code uses public entry files while implementation stays in subfolders. Add checks, a starter package, and documentation, then verify that forbidden imports fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preventing imports into package internals
• Adding boundary checks to existing validation commands
• Creating a starter package with public entry files

Set up the repository settings that engineering skills read: where work is tracked, which triage labels to use, and where domain documents belong. Review existing files and confirm drafts before writing configuration documents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a repository before using engineering skills
• Configure GitHub, GitLab, or local Markdown issue tracking
• Match triage labels to an existing workflow

Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a workflow for turning an idea into working software
• Find the starting point for a difficult bug investigation
• Plan specifications and tickets for work across multiple sessions

Implement work described in a specification or set of tickets, using test-first development where agreed. Run type checks and tests throughout, review the completed changes, and commit the work to the current branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing work from a specification
• Completing a set of development tickets
• Checking changes with types and tests

Turn an existing conversation and codebase context into a feature specification. Organize user needs, implementation decisions, testing plans, and scope, then publish the specification to the project’s issue tracker with a label marking it ready for agent work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a feature discussion into a specification
• Recording implementation and testing decisions
• Publishing an issue ready for agent work

Draft or revise pull request descriptions that show the change, evidence of its behavior, and merge risks. Use concise diagrams, trees, or diffs alongside before-and-after results to help reviewers assess impact and how easily changes can be reversed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a description for a pull request
• Explain a refactor with a tree or diff
• Present before-and-after evidence for a fix