Phase 3: Dependency decomposition. Only invoke when explicitly requested by the user or by the yoink orchestrator.
中文简介正在准备中。当前显示原文说明。
Phase 2: Generate and discover tests, validate against real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Do not invoke this skill unless explicitly requested. It is called by
/yoink:yoinkor run standalone by the user.
Prerequisite: /yoink:setup must have been run first (reference dir and real library must exist).
Parse your prompt to identify:
Package: line or --package argumentTask: line or prompt bodyNaming convention:
yoink_<package>/where<package>has hyphens replaced by underscores (e.g., packagelitellm->yoink_litellm/).
--skip-test-discoverer is present then skip to step 2.Use the yoink:test-discoverer agent to search for relevant tests from the original library's test suite.
Pass input as JSON:
{
"package_name": "<PACKAGE>",
"target_function": "<TARGET_FUNCTION>"
}
Discovered tests are reference material only. They exist so the test-generator can study real-world patterns and assertions. They are never executed during validation or any later step -- only generated tests are run.
Use the yoink:test-generator agent to write original pytest tests for the target function.
Pass input as JSON:
{
"package_name": "<PACKAGE>",
"target_function": "<TARGET_FUNCTION>"
}
Run only the generated tests using the script below against the installed real library. Do NOT run discovered tests -- they are reference only and may depend on API keys, network access, or fixtures that are not available.
uv run ${CLAUDE_PLUGIN_ROOT}/scripts/run_tests.py --project-dir . 2>&1
After validation passes, rewrite imports in generated tests so they target yoink_<package>/:
uv run ${CLAUDE_PLUGIN_ROOT}/scripts/rewrite_imports.py --package <PACKAGE> --target-dir yoink_<PACKAGE>/tests/generated
Run the test suite against the empty yoink_<package>/ to confirm tests fail:
uv run ${CLAUDE_PLUGIN_ROOT}/scripts/run_tests.py --project-dir . --summary-only
Score should be ~0.0 (tests should fail against empty yoink_<package>/).
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Phase 3: Dependency decomposition. Only invoke when explicitly requested by the user or by the yoink orchestrator.
中文简介正在准备中。当前显示原文说明。
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
中文简介正在准备中。当前显示原文说明。
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
中文简介正在准备中。当前显示原文说明。
Scaffold project: clone repo, install real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.
中文简介正在准备中。当前显示原文说明。
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
中文简介正在准备中。当前显示原文说明。
Curate tests then decompose dependencies
中文简介正在准备中。当前显示原文说明。