원클릭으로 Manus에서 모든 스킬 실행

content

스타13

포크1

업데이트2026년 7월 11일 02:59

Validate, install, update, list, rescan, remove, and reveal data-only Pulp content packs for installed plugins. Use for presets, themes, samples, wavetables, and other end-user data that must be reviewed before install or update.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

danielraffel

danielraffel/pulp

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Pulp Content

Use this skill when a user has a .pulpcontent archive or local content-pack directory for an installed plugin.

Content packs are valuable because:

plugin authors ship presets, themes, samples, and wavetables without custom installers;
users get validation, a visible target plugin/content path, and reversible removal;
runtime plugins consume installed data through ContentRegistry or PresetManager content capabilities.

Trust Boundary

pulp add <name> is for curated developer dependency packages.

pulp kit ... is for developer artifacts that may transform a project.

pulp content ... is for end-user data installed into a plugin-specific content directory.

Trust rules:

content commands copy data only; they never run package CMake, JavaScript, scripts, dynamic libraries, or network fetches;
.pulpcontent archives must include files.sha256.json, and every payload file must be listed and hash-matched before preview/install/update;
update uses an explicit local path, not registry resolution, and rolls back a replaced version on failure;
install/update/remove/reveal require safe single-component plugin/package/version ids;
rescan is metadata-only and records plugin_id plus manifest_sha256;
removal deletes only the installed pack root; user edits stay in the plugin's normal user preset path. The OK line names the deleted pack path — Removed content pack <id> for <plugin> (removed <path>) — for parity with tool uninstall.

Built plugins should embed pulp.plugin-runtime.json via pulp_add_plugin(... CONTENT_CAPABILITIES ... CONTENT_KINDS ...). Agents and in-app installers should preview with that manifest before approval, then install with approved=true. Validate built bundles with ValidationHarness::validate_plugin_runtime_manifest(...).

Commands

./build/pulp content validate <path> --json
./build/pulp content preview <path> --plugin-runtime <manifest> --json
./build/pulp content install <path> --plugin <plugin-id> --yes
./build/pulp content update <path> --plugin <plugin-id> --yes
./build/pulp content list --plugin <plugin-id> --json
./build/pulp content rescan --json
./build/pulp content reveal <package-id> --plugin <plugin-id> --version <version>
./build/pulp content remove <package-id> --plugin <plugin-id> --version <version> --yes

Use --root <dir> only for tests, CI, or explicit sandboxing. Normal installs use the platform user-data root.

Agent Workflow

Validate the pack.
Preview against the trusted plugin runtime manifest when available, and explain content id, version, capabilities, target plugin, supported kinds, and reload/restart policy.
Preview the install root using reveal or the install plan text.
Install or update only after explicit approval with --yes.
Use rescan when the index is missing/stale or after manual repair.
Remove only after explicit approval with --yes.
Never delete user-created presets or files outside the installed pack root.

Use MCP tools when available:

pulp_content_validate
pulp_content_preview
pulp_content_install
pulp_content_update
pulp_content_list
pulp_content_rescan
pulp_content_remove
pulp_content_reveal

Related extend surfaces

packages, kits, content, and installable-tools are Pulp's four ways to extend a project or machine, and they share one lifecycle contract: add is validated, remove is confirmed + confined to the surface's own area + names what it deleted, and both add and remove ship tests. Pick the right surface and read the shared contract in extending-pulp.md.

packages — third-party audio DSP libraries → a project
kits — reusable Pulp code/UI/templates → a project
content — data-only packs (presets/samples) → an installed plugin
installable-tools — machine-level dev/agent tooling under ~/.pulp/tools/, plus the shared validate-and-uninstall-from-outside-a-checkout bar

이 저장소의 다른 Skills

같은 저장소

timebase

danielraffel/pulp

Pulp musical/media time primitives, immutable compiled tempo maps, monotonic transport beats, exact sample anchors, corrected inverse conversion, and shared transport quantization arithmetic.

2026-07-1913

import-design

danielraffel/pulp

Import designs from Figma, Stitch, v0, Pencil, React Native, or Claude Design into Pulp web-compat JS with automated visual validation. Claude Design imports also scaffold a pulp::view::EditorBridge handler file. Versioned parser, format, and compatibility-schema detection lives behind `--detect-only` and `--report-new-format`.

2026-07-1913

streams

danielraffel/pulp

Pick the right Pulp Stream for a given I/O task, wire async callbacks correctly without deadlocking the worker, and avoid the backpressure / cancellation footguns in `pulp::runtime::AsyncStream`.

2026-07-1913

view-bridge

danielraffel/pulp

Editor lifecycle and multi-view attach for Pulp plugins — when to override Processor::create_view(), the open → notify_attached → resize → close protocol, release_view() ownership rules, and secondary-view roles.

2026-07-1913

hosting

danielraffel/pulp

Load, run, and test VST3 / AU / CLAP / LV2 plugins from Pulp code. Use when working on `core/host/` (scanner, plugin_slot, signal_graph), when adding a new format backend, when wiring a plugin into a SignalGraph, or when writing an integration test that needs a real plug-in binary.

2026-07-1913

auv3

danielraffel/pulp

Audio Unit v3 (AUAudioUnit) format adapter for Pulp — render-block wiring, parameter tree bridging, MIDI / sysex via AURenderEvent, sidechain pulls, state persistence, iOS extension surface, and the pitfalls discovered while wiring the adapter.

2026-07-1913

name	content
description	Validate, install, update, list, rescan, remove, and reveal data-only Pulp content packs for installed plugins. Use for presets, themes, samples, wavetables, and other end-user data that must be reviewed before install or update.
requires	{"scripts":["tools/kits/pulp-package.schema.json","tools/kits/pulp-plugin-runtime.schema.json"]}

Pulp Content

Use this skill when a user has a .pulpcontent archive or local content-pack directory for an installed plugin.

Content packs are valuable because:

plugin authors ship presets, themes, samples, and wavetables without custom installers;
users get validation, a visible target plugin/content path, and reversible removal;
runtime plugins consume installed data through ContentRegistry or PresetManager content capabilities.

Trust Boundary

pulp add <name> is for curated developer dependency packages.

pulp kit ... is for developer artifacts that may transform a project.

pulp content ... is for end-user data installed into a plugin-specific content directory.

Trust rules:

content commands copy data only; they never run package CMake, JavaScript, scripts, dynamic libraries, or network fetches;
.pulpcontent archives must include files.sha256.json, and every payload file must be listed and hash-matched before preview/install/update;
update uses an explicit local path, not registry resolution, and rolls back a replaced version on failure;
install/update/remove/reveal require safe single-component plugin/package/version ids;
rescan is metadata-only and records plugin_id plus manifest_sha256;
removal deletes only the installed pack root; user edits stay in the plugin's normal user preset path. The OK line names the deleted pack path — Removed content pack <id> for <plugin> (removed <path>) — for parity with tool uninstall.

Commands

./build/pulp content validate <path> --json
./build/pulp content preview <path> --plugin-runtime <manifest> --json
./build/pulp content install <path> --plugin <plugin-id> --yes
./build/pulp content update <path> --plugin <plugin-id> --yes
./build/pulp content list --plugin <plugin-id> --json
./build/pulp content rescan --json
./build/pulp content reveal <package-id> --plugin <plugin-id> --version <version>
./build/pulp content remove <package-id> --plugin <plugin-id> --version <version> --yes

Use --root <dir> only for tests, CI, or explicit sandboxing. Normal installs use the platform user-data root.

Agent Workflow

Validate the pack.
Preview against the trusted plugin runtime manifest when available, and explain content id, version, capabilities, target plugin, supported kinds, and reload/restart policy.
Preview the install root using reveal or the install plan text.
Install or update only after explicit approval with --yes.
Use rescan when the index is missing/stale or after manual repair.
Remove only after explicit approval with --yes.
Never delete user-created presets or files outside the installed pack root.

Use MCP tools when available:

pulp_content_validate
pulp_content_preview
pulp_content_install
pulp_content_update
pulp_content_list
pulp_content_rescan
pulp_content_remove
pulp_content_reveal

Related extend surfaces

packages — third-party audio DSP libraries → a project
kits — reusable Pulp code/UI/templates → a project
content — data-only packs (presets/samples) → an installed plugin
installable-tools — machine-level dev/agent tooling under ~/.pulp/tools/, plus the shared validate-and-uninstall-from-outside-a-checkout bar