Agent Skills: skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
ID: Jst-Well-Dan/Skill-Box/skill-creator
84
Install this agent skill to your local
Skill Files
The files that make up skill-creator.
Loading file tree…
More agent skills
- 1k-perps-moduleUse for OneKey Perps/Hyperliquid development/review: views/Perp, ServiceHyperLiquid, 永续合约, 订单簿, orderbook, TWAP, scale, Chase, Relay/Unifold deposits, signing, charts or layouts. Excludes generic Swap/Market.
- slackSlack messaging workflows through OpenClaw's message tool.
- writing-streamlit-appsWrite Streamlit app source code that runs well in a PostHog sandbox — the posthog_apps.query() bridge for reading PostHog data, the packages baked into the sandbox image, caching and session state across Streamlit reruns, layout and chart patterns, and the app.py entry point with any helper modules and data files bundled beside it. Use when authoring or debugging the Python source of a PostHog Streamlit app, when a query inside an app fails, or when asked to "write a streamlit app that shows PostHog data".
- codebase-onboarding不慣れなコードベースを分析し、アーキテクチャマップ、主要なエントリポイント、規約、スターターCLAUDE.mdを含む構造化オンボーディングガイドを生成します。新しいプロジェクトに参加するか、リポでClaude Codeを初めてセットアップする場合に使用します。
- hf-cloud-python-env-setupSet up an isolated Python environment for SageMaker / AWS work, with the right Python version and current boto3. Use this skill whenever Python code will be executed for a SageMaker deployment, training job, or any AWS automation — including when about to run `pip install`, when about to invoke `boto3`, when creating or activating a virtualenv, or when the user asks to "set up the environment". Never use system Python and never `pip install` into it. Always isolate. This skill prevents the most common failure modes: wrong Python version, dependency conflicts, and stale SDKs.
- ce-debugDiagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.