setup-provider-r2

Name: setup-provider-r2
Availability: InStock
Author: tachiiri-org

Configure R2 provider settings and add adapter boundary scaffolding.

Updated Feb 28, 2026

Search Tags:#integration #scaffolding #r2 #repository setup #adapter #provider setup

Ready to run

npx skills add https://github.com/tachiiri-org/agent-ops --skill setup-provider-r2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-provider-r2
Source: https://github.com/tachiiri-org/agent-ops/tree/main/.codex/skills/setup-provider-r2
Command: npx skills add https://github.com/tachiiri-org/agent-ops --skill setup-provider-r2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of setting up R2 provider configurations and essential scaffolding within adapter repositories that directly integrate with R2.

Core Features & Use Cases

R2 Integration Guidance: Provides specific instructions and boundary-specific scaffolding for R2 integration.
Adapter Boundary Focus: Ensures setup is relevant only for repositories acting as adapters to R2.
Use Case: When onboarding a new repository that needs to interface directly with R2, this Skill automates the initial setup, ensuring compliance with R2 integration principles.

Quick Start

Run the setup-provider-r2 skill to add R2 scaffolding to this adapter repository.

Frequently Asked Questions about setup-provider-r2

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

FAQPage Schema

How do I set up R2 provider scaffolding for an adapter repository?▼

To set up R2 provider scaffolding, run the setup-provider-r2 skill which verifies direct R2 integration and adds minimal boundary-specific scaffolding, followed by standard validation commands to ensure proper configuration.

What is R2 integration scaffolding and when do I need it?▼

R2 integration scaffolding is the minimal configuration and boundary setup needed when a repository acts as a direct adapter to R2. You need it when onboarding a new repository that interfaces directly with R2 at the adapter boundary.

Does this R2 provider setup work for any repository or only adapter boundaries?▼

This R2 provider setup works exclusively for repositories acting as adapters to R2 at the adapter boundary. It verifies direct R2 integration and applies only boundary-specific scaffolding, not general repository configuration.

What's the best way to configure R2 provider settings for a new adapter?▼

The best way to configure R2 provider settings is to run the setup skill which automates initial setup, applies boundary-specific scaffolding, verifies direct integration, and runs standard validation commands for compliance.

What happens after R2 scaffolding is applied to my repository?▼

After R2 scaffolding is applied, the skill runs standard validation commands to verify the setup. This ensures the adapter repository complies with R2 integration principles and the boundary-specific configuration is correct.

Can I use this setup if my repository integrates with R2 indirectly?▼

No, this setup is specifically designed for repositories with direct R2 integration at the adapter boundary. The skill verifies direct R2 integration before applying any scaffolding, making it unsuitable for indirect integration patterns.