Openclaw용 Box SDK Development

Build and debug reliable Box SDK integrations with version-aware guidance for transfers, bulk operations, rate limits, and observability.

iskysun96
v1.0.0
Oct 15, 2026
0
63
0

설치 및 다운로드

1. ClawHub CLI

레지스트리에서 스킬을 바로 설치하는 가장 빠른 방법입니다.

npx clawhub@latest install box-sdk-development

2. 수동 설치

스킬 폴더를 다음 위치 중 하나로 복사하세요

글로벌
~/.openclaw/skills/
워크스페이스
<project>/skills/

우선순위: 워크스페이스 > 로컬 > 번들

3. 프롬프트 설치

이 프롬프트를 OpenClaw에 복사하면 자동으로 설치됩니다.

Clawhub를 사용해서 box-sdk-development 설치를 도와줘. Clawhub가 설치되어 있지 않다면 먼저 설치해 줘 (npm i -g clawhub).

다운로드를 원하시나요?

ZIP 아카이브 형태의 원본 스킬 파일을 받으세요.

Box SDK Development란 무엇인가요?

Box SDK Development helps coding agents implement and troubleshoot application code that uses official Box SDKs, especially Python and TypeScript/Node. It prioritizes the project's installed SDK version, verifies method signatures and behavior against current references, and distinguishes operations such as downloading original content, retrieving previews, and listing files.

As one of the Openclaw Skills for cloud application development, it guides developers toward safe, efficient Box integrations: reuse clients and token caches, control request volume, handle retries carefully, protect credentials, and verify behavior with focused tests. It is intended for SDK-based application work, not one-off CLI or MCP content operations.

Box SDK Development 활용 사례

  • Implement or debug Box API calls in an existing Python or TypeScript/Node application.
  • Upload or download files while selecting the correct endpoint and validating transfer behavior.
  • Process large collections with pagination, bounded concurrency, and durable per-item outcomes.
  • Track Box changes using events or webhooks with catch-up instead of repeated full scans.
  • Diagnose rate limiting, authentication failures, unexpected API usage, or duplicate request paths.
  • Add safe SDK instrumentation and report what was tested, what remains unverified, and the workload assumptions.

Box SDK Development 작동 원리

  1. Inspect the installed SDK version, language runtime, authentication method, Box actor, client wrapper, and expected workload; preserve the current SDK major version unless a migration is needed or requested.
  2. Trace request paths and decide where client reuse, token caching, rate limiting, retries, and logging belong. Estimate calls, throughput, transfer size, and restart requirements for repeated or bulk work.
  3. Choose the API operation that matches the desired result: original file bytes, a preview representation, metadata, or a listing. Request necessary fields and paginate until the endpoint's actual end.
  4. Confirm method arguments, return types, pagination behavior, and errors against the installed SDK and relevant Box documentation. Keep Python and Node SDK interfaces distinct.
  5. Implement with least privilege, bounded concurrency, and one clear retry owner. Honor Retry-After, reconcile uncertain writes before retrying, and diagnose unchanged 401/403 failures rather than repeating them.
  6. Add focused tests and run the project's type check or build. When possible, verify permissions and transfer behavior using an authorized test account.
  7. Instrument operations and, for bulk work, record durable item outcomes and monitor throughput and call usage. Finish with a concise report of changes, verification, design tradeoffs, call-budget assumptions, and unverified behavior.

Box SDK Development 설정 가이드

This skill provides implementation guidance; it does not prescribe a separate skill installer or require a fixed project configuration. Start in the Box-integrated project and inspect its existing dependencies, authentication, and client wrapper before changing anything. Keep the project's current SDK major version unless migration is explicitly required.

Choose the reference that matches the installed SDK and task:

  • Python: references/python.md
  • TypeScript/Node: references/typescript.md
  • Collection-wide jobs: references/bulk-operations.md
  • Uploads or downloads: references/file-transfer.md

Use the project's existing package manager and documented setup rather than copying commands or interfaces from another SDK version. For official sources, consult the Box Node SDK, Box Python SDK, and Box API reference.

# Inspect project files and the installed Box SDK using your project's package manager.
# Then run the focused tests and the project's type check or build.

Keep client secrets and service-account keys on the server, use the intended Box actor with least privilege, and never log credentials.

Box SDK Development 데이터 스키마 및 분류 체계

The skill defines no fixed output directory, generated file format, or application database schema. It recommends organizing implementation and operational data around the following fields:

Record or concern Recommended details
Operation telemetry Operation name, item ID, safe actor or tenant ID, status, Box request ID when available, duration, and relevant byte count
Job tracking Job ID, throughput, call-budget assumptions, and durable per-item success or failure outcomes
Throttling and retries 429 occurrences and retry delay when SDK hooks or transport instrumentation expose them; hidden retries must be treated as unknown
Pagination and discovery Required fields, endpoint-specific pagination behavior, and markers where supported for large or changing collections
Sensitive data handling Exclude file content, credentials, and signed URLs; configure log volume and retention

For collection-wide work, preserve per-item outcomes so jobs can be monitored and safely resumed or reconciled. Reuse the SDK client and token cache, and account for authentication, discovery, retries, and verification in API-call estimates.

Box SDK Development 고급 기능

  • Version-aware implementation guidance for Python and TypeScript/Node SDKs, including a warning not to transfer method calls across incompatible SDK majors.
  • Bulk-operation planning with call estimates, bounded concurrency, progress monitoring, and durable per-item results.
  • Rate-limit handling that checks SDK retry behavior, respects Retry-After, and avoids competing retry owners.
  • Safer write recovery by reconciling uncertain outcomes before retrying; distinguishes throttling from 401/403 errors.
  • Change-tracking guidance that favors events or webhooks with catch-up over repeated full scans.
  • Observability guidance for request IDs, operation outcomes, timing, transfer bytes, throttling, and job-level usage without exposing sensitive data.
  • Design recommendations to use Box-side copy, move, or metadata operations when content remains in Box.
  • Completion reporting that captures verification, design decisions, alternatives and tradeoffs, bulk call-budget assumptions, and unverified behavior.

SKILL.md


로드 중

관련 Openclaw 스킬

METADATA

Github Stars: 0
forks: 0

추천*