gos-configurar-paperclip

Configure Paperclip deployments with YAML deep-merge patches and dry-run validation.

41|27|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kcleto-ai/growth-os-skills --skill gos-configurar-paperclip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gos-configurar-paperclip
Source: https://github.com/kcleto-ai/growth-os-skills/tree/main/.claude/skills/gos-configurar-paperclip
Command: npx skills add https://github.com/kcleto-ai/growth-os-skills --skill gos-configurar-paperclip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruamel.yaml, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill guides configuring, optimizing, and auditing a Paperclip instance to reduce token costs and improve reliability across local-native, local-docker, ssh-native, and ssh-docker deployment modes.

Core Features & Use Cases

  • Automated patching workflow: backup, YAML deep-merge patches, and dry-run validation before import.
  • Centralized cost optimization: budget enforcement, routing hints, and heartbeat tuning for tokens saved.
  • Cross-environment support: works with CLI-based onboard/setup and remote SSH orchestration.

Quick Start

Run the patch cycle: backup, patch, dry-run import, review, and apply to bring Paperclip configuration into compliance.

Frequently Asked Questions about gos-configurar-paperclip

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Paperclip to reduce token costs across different deployment modes?▼

To optimize Paperclip token costs, you configure a .paperclip.yaml base file with budget enforcement, routing hints, and heartbeat tuning. This works across local-native, local-docker, ssh-native, and ssh-docker modes.

How does YAML deep-merge patching work for Paperclip configurations?▼

YAML deep-merge patching works by applying configuration snippets to your base .paperclip.yaml file. The workflow involves backing up, deep-merging patches, and running a dry-run import validation before applying changes.

Can I use SSH to orchestrate Paperclip configuration on remote servers?▼

Yes, you can use SSH orchestration to configure remote Paperclip instances. The Skill supports ssh-native and ssh-docker modes for remote setup, patching, and audit workflows.

What is the recommended workflow to audit and patch a Paperclip instance safely?▼

The recommended workflow is to backup, patch, dry-run import, review, and apply. This doctor and import validation cycle ensures your Paperclip configuration changes are safe before deployment.

Do I need ruamel.yaml or pyyaml to manage Paperclip configuration patches?▼

Yes, you need ruamel.yaml and pyyaml dependencies to manage Paperclip configuration patches. These libraries enable the YAML deep-merge patching and validation cycle for your .paperclip.yaml files.

What are the limitations when tuning heartbeat and concurrency settings in Paperclip?▼

Heartbeat and concurrency tuning in Paperclip is limited by your deployment mode and budget constraints. Settings are enforced through the .paperclip.yaml configuration, requiring dry-run validation to prevent routing conflicts.