agentleFS
sdbdssdbds/ACE-Step-1.5-for-windows/.claude/skills/acestep-docs/SKILL.md

acestep-docs

Skill101 starsChanged 8 months agoMITView on GitHub

ACE-Step documentation and troubleshooting. Use when users ask about installing ACE-Step, GPU configuration, model download, Gradio UI usage, API integration, or troubleshooting issues like VRAM problems, CUDA errors, or model loading failures.

3 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

Files
SKILL.md

ACE-Step Documentation

Documentation skill for ACE-Step music generation system.

Quick Reference

Getting Started

DocumentDescription
README.mdInstallation, model download, startup commands
Tutorial.mdGetting started tutorial, best practices
ABOUT.mdProject overview, architecture, model zoo

Guides

DocumentDescription
GRADIO_GUIDE.mdWeb UI usage guide
INFERENCE.mdInference parameters tuning
GPU_COMPATIBILITY.mdGPU/VRAM configuration, hardware recommendations
ENVIRONMENT_SETUP.mdEnvironment detection, uv installation, python_embeded setup (Windows/Linux/macOS)
SCRIPT_CONFIGURATION.mdConfiguring launch scripts: .bat (Windows) and .sh (Linux/macOS)
UPDATE_AND_BACKUP.mdGit updates, file backup, conflict resolution (all platforms)

API (for developers)

DocumentDescription
API.mdREST API documentation
Openrouter_API.mdOpenRouter API integration

Instructions

  1. Installation questions → read getting-started/README.md
  2. General usage / best practices → read getting-started/Tutorial.md
  3. Project overview / architecture → read getting-started/ABOUT.md
  4. Web UI questions → read guides/GRADIO_GUIDE.md
  5. Inference parameter tuning → read guides/INFERENCE.md
  6. GPU/VRAM issues → read guides/GPU_COMPATIBILITY.md
  7. Environment setup (uv, python_embeded) → read guides/ENVIRONMENT_SETUP.md
  8. Launch script configuration (.bat/.sh) → read guides/SCRIPT_CONFIGURATION.md
  9. Updates and backup → read guides/UPDATE_AND_BACKUP.md
  10. API development → read api/API.md or api/Openrouter_API.md

Common Issues

  • Installation problems: See getting-started/README.md
  • VRAM insufficient: See guides/GPU_COMPATIBILITY.md
  • Model download failed: See getting-started/README.md or guides/SCRIPT_CONFIGURATION.md
  • uv not found: See guides/ENVIRONMENT_SETUP.md
  • Environment detection issues: See guides/ENVIRONMENT_SETUP.md
  • BAT/SH script configuration: See guides/SCRIPT_CONFIGURATION.md
  • Update and backup: See guides/UPDATE_AND_BACKUP.md
  • Update conflicts: See guides/UPDATE_AND_BACKUP.md
  • Inference quality issues: See guides/INFERENCE.md
  • Gradio UI not starting: See guides/GRADIO_GUIDE.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.