vamseeachanta
vamseeachanta/workspace-hub
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill discipline-refactor-phase-2-planning命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
基于 SOC 职业分类
正在显示 SKILL.md
| name | discipline-refactor-phase-2-planning |
| description | Sub-skill of discipline-refactor: Phase 2: Planning. |
| version | 2.0.0 |
| category | _internal |
| type | reference |
| scripts_exempt | true |
Spawn: Task with subagent_type=Plan
Call: @skill-creator for new discipline skills
Prompt:
Create module-based migration plan based on Phase 1 analysis.
Context: {analysis_results}
Create plan for ALL directories:
1. Package identification:
- Confirm package name: <package_name>
- Confirm disciplines: [_core, discipline-1, discipline-2, ...]
2. Code structure (src/):
BEFORE: src/<package>/feature1/, src/<package>/feature2/
AFTER: src/<package>/modules/_core/, src/<package>/modules/<discipline>/
3. Test structure:
BEFORE: tests/test_feature1.py, tests/integration/
AFTER: tests/modules/_core/, tests/modules/<discipline>/
4. Documentation structure:
BEFORE: docs/api/, docs/guides/
AFTER: docs/modules/_core/, docs/modules/<discipline>/
5. Specs structure:
BEFORE: specs/feature-spec.md, specs/plan.md
AFTER: specs/modules/<discipline>/, specs/templates/
6. Data structure (if exists):
BEFORE: data/raw/, data/processed/
AFTER: data/modules/<discipline>/
7. Skills structure:
BEFORE: .Codex/skills/category/
AFTER: .Codex/skills/<discipline>/
8. Import updates:
- from <package>.feature → from <package>.modules.<discipline>
- Update __init__.py files
- Update relative imports
9. Create README.md for each module with:
- Module purpose
- Key files
- Dependencies on other modules
Output executable task list for Phase 3.