What makes Poyo Replace Section notable?

1.1K downloads. Trust evidence available

How should Poyo Replace Section be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Poyo Replace Section

Replace a section of generated music on PoYo / poyo.ai via `https://api.poyo.ai/api/generate/submit`; use for `replace-section`, music section editing, infil...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.0.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.1release · observed Jul 9, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s177pant1v4gn5k13ffg1fp5b183nb02:poyo-replace-section

Install using `clawhub skill install s177pant1v4gn5k13ffg1fp5b183nb02:poyo-replace-section` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/coolhackboy/poyo-replace-section before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-coolhackboy-poyo-replace-section/snapshot"

Documentation

CLAWHUB

18,704 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: poyo-replace-section
description: Replace a section of generated music on PoYo / poyo.ai via `https://api.poyo.ai/api/generate/submit`; use for `replace-section`, music section editing, infill_start_s, infill_end_s, task_id plus audio_id inputs, callbacks, and music detail retrieval.
metadata: {"openclaw":{"homepage":"https://poyo.ai/models/replace-section","requires":{"bins":["curl"],"env":["POYO_API_KEY"]},"primaryEnv":"POYO_API_KEY"}}
---

# PoYo Replace Section

## PoYo Links

- Model page: <https://poyo.ai/models/replace-section>
- API docs: <https://docs.poyo.ai/api-manual/music-series/replace-section>
- API key page: <https://poyo.ai/dashboard/api-key>

Use this skill for `replace-section` jobs on PoYo. It helps agents prepare music section replacement payloads, define an exact time range, submit async requests, and explain result retrieval.

## Use When

- The user explicitly wants to replace a section of an existing PoYo-generated music track.
- The user has a completed PoYo music `task_id` and `audio_id` and asks for an edit payload, server-side curl command, callback setup, or result retrieval.
- The user has already chosen PoYo as the execution provider for a music editing workflow.

## Model Selection

- `replace-section`: use for replacing a time range in a generated music track with new musical content.

## Key Inputs

- `task_id` identifies the completed source music generation task.
- `audio_id` identifies the specific audio track to edit.
- `prompt` describes the replacement content.
- `tags` describe style or mood for the replacement section.
- `title` names the resulting track.
- `infill_start_s` and `infill_end_s` define the section to replace in seconds.
- `full_lyrics` is required by the documented schema when the workflow modifies lyrics.
- `callback_url` is optional and useful for production queues.

## Security Rules

- Treat `POYO_API_KEY` as a secret.
- Keep PoYo API keys in server-side environment variables or a backend secret manager.
- Never place an API key in browser code, frontend bundles, public repositories, logs, screenshots, or chat output.
- Do not log private prompts, lyrics, customer task ids, audio identifiers, generated file URLs, callback URLs, or raw authorization headers unless the product policy allows it.
- Do not use this skill for generic music editing unless the user explicitly wants a PoYo Replace Section API workflow.
- Do not make live API calls unless the user explicitly asks, confirms the payload should be sent to PoYo, and provides a safe server-side environment.

## Execution

- Read `references/api.md` for endpoint details, request fields, examples, and result retrieval notes.
- Use `scripts/submit_replace_section.sh` only when the user wants to submit a prepared JSON payload from a trusted shell.
- If the user only needs a curl example, adapt one from `references/api.md`.
- After submission, report the returned `task_id` clearly so follow-up retrieval is easy.

## Output Expect

_meta.json

{
  "ownerId": "kn7f14qr8xdf5gs6pr7cm7p97h82m349",
  "slug": "poyo-replace-section",
  "version": "1.0.1",
  "publishedAt": 1783563104102
}

references/api.md

# PoYo Replace Section API Reference

## Endpoint

- Submit task: `POST https://api.poyo.ai/api/generate/submit`
- Status query: `GET https://api.poyo.ai/api/generate/status/{task_id}`
- Source docs: <https://docs.poyo.ai/api-manual/music-series/replace-section>
- OpenAPI JSON: <https://docs.poyo.ai/api-manual/music-series/replace-section.json>
- Model page: <https://poyo.ai/models/replace-section>

## Auth

Send:

```http
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
```

Get API keys from <https://poyo.ai/dashboard/api-key>.

Recommended skill env var:

- `POYO_API_KEY`

## Model

- `replace-section`: replace a specific time range of an existing generated music track with new content.

## Request Schema

Top-level fields:

- `model` string, required
- `callback_url` string URI, optional
- `input` object, required

Required `input` fields:

- `task_id` string
- `audio_id` string
- `prompt` string
- `tags` string
- `title` string
- `infill_start_s` number
- `infill_end_s` number
- `full_lyrics` string

Optional `input` fields:

- `negative_tags` string

Always verify current field support in the PoYo docs before relying on model-specific options.

## Submit Example

```bash
curl --fail-with-body --request POST \
  --url "https://api.poyo.ai/api/generate/submit" \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "model": "replace-section",
    "callback_url": "https://example.com/api/poyo/webhook",
    "input": {
      "task_id": "music_task_example",
      "audio_id": "audio_track_example",
      "prompt": "A brighter chorus with a clean vocal hook",
      "tags": "pop, upbeat",
      "title": "Edited Chorus",
      "infill_start_s": 30.0,
      "infill_end_s": 60.0,
      "full_lyrics": "Complete lyrics for the edited track"
    }
  }'
```

## Typical Submit Response

```json
{
  "code": 200,
  "data": {
    "task_id": "replacement_task_example",
    "status": "not_started",
    "created_time": "2026-07-09T08:00:00"
  }
}
```

## Status Query Example

```bash
curl --fail-with-body --request GET \
  --url "https://api.poyo.ai/api/generate/status/replacement_task_example" \
  --header "Authorization: Bearer YOUR_API_KEY"
```

## Practical Guidance

- Use a completed source music task id and a matching audio identifier.
- Ensure `infill_end_s` is greater than `infill_start_s`.
- Keep the replacement range narrow enough for the intended edit.
- Save `data.task_id` immediately after submission.
- Use `callback_url` for production queues and longer user workflows.
- Keep private prompts, lyrics, task ids, audio identifiers, callback URLs, and generated file URLs out of logs.

skill-card.md

## Description:

Replace a section of generated music on PoYo / poyo.ai via `https://api.poyo.ai/api/generate/submit`; use for `replace-section`, music section editing, infill_start_s, infill_end_s, task_id plus audio_id inputs, callbacks, and music detail retrieval.

This skill is ready for commercial/non-commercial use.

## Publisher:

[coolhackboy](https://clawhub.ai/user/coolhackboy)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and agents use this skill to prepare and submit PoYo Replace Section music-editing payloads, including source task identifiers, replacement time ranges, prompts, lyrics, callback configuration, and status retrieval.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: API credentials could be exposed if POYO_API_KEY or authorization headers are copied into client code, logs, repositories, screenshots, or chat output.

Mitigation: Keep POYO_API_KEY in server-side environment variables or a backend secret manager, and avoid logging raw authorization headers.

Risk: Private prompts, lyrics, task IDs, audio IDs, generated URLs, or callback URLs may contain sensitive project or user data.

Mitigation: Review payload JSON before submission and send private content to PoYo only when appropriate for the user's workflow and policy.

Risk: Submitting a malformed replacement range can edit the wrong section or fail the API request.

Mitigation: Confirm that infill_end_s is greater than infill_start_s and that the source task_id and audio_id match the intended completed track before live submission.

## Reference(s):

- [PoYo Replace Section API Reference](references/api.md)
- [PoYo Replace Section model page](https://poyo.ai/models/replace-section)
- [PoYo Replace Section API docs](https://docs.poyo.ai/api-manual/music-series/replace-section)
- [PoYo Replace Section OpenAPI JSON](https://docs.poyo.ai/api-manual/music-series/replace-section.json)
- [ClawHub skill page](https://clawhub.ai/coolhackboy/skills/poyo-replace-section)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, guidance]

**Output Format:** [Markdown with JSON payload examples and bash commands]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May include PoYo model id, source task and audio identifiers, replacement time range, payload summary, returned task id, and next-step status or webhook guidance.]

## Skill Version(s):

1.0.1 (source: server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.