返回 Skill 列表
extension
分类: 开发与工程无需 API Key

shelby-expert

精通Aptos区块链上的Shelby协议去中心化块存储。协调涵盖协议架构、SDK使用、智能合约、CLI工具、RPC基础设施、dApp构建和存储集成的7个专业子技能。触发关键词包括Shelby协议、Shelby存储、去中心化存储、Aptos存储、块存储、Shelby。

person作者: jakexiaohubgithub

Shelby Protocol Expert

Purpose

Provide expert guidance on Shelby Protocol decentralized blob storage system on Aptos blockchain. Coordinates 7 specialized sub-skills to cover all aspects of the protocol.

When to Use

Auto-invoke when users mention:

  • Shelby - media player, platform, integration
  • Media - video, audio, streaming, playback
  • SDK - integration, API, TypeScript, JavaScript
  • Features - playlists, chapters, subtitles, live streaming
  • CLI - command-line tools, scripts

Knowledge Base

Documentation is stored in TOON format (40-60% token savings):

  • Location: docs/
  • Index: docs/INDEX.md
  • Format: .toon or .md files

Process

When a user asks about Shelby:

1. Identify Topic

Common topics:
- Getting started / setup
- SDK integration (React, Vue, vanilla JS)
- Media player configuration
- Streaming protocols (HLS, DASH)
- Playlist management
- Custom UI components
- CLI usage
- API reference

2. Search Documentation

Use Grep to find relevant docs:

# Search for specific topics
Grep "sdk|integration" docs/ --output-mode files_with_matches
Grep "streaming|playback" docs/ --output-mode content -C 3

Check the INDEX.md for navigation:

Read docs/INDEX.md

3. Read Relevant Files

Read the most relevant documentation files:

Read docs/path/to/relevant-doc.md
# or .toon format if available

4. Provide Answer

Structure your response:

  • Direct answer - solve the user's problem first
  • Code examples - show integration code when applicable
  • Configuration - provide setup instructions
  • References - cite specific docs (file paths) for deeper reading
  • Best practices - mention Shelby-specific patterns

Example Workflows

Example 1: Basic Integration

User: "How do I integrate Shelby into my React app?"

1. Search: Grep "react|integration" docs/
2. Read: Integration guide
3. Answer:
   - Show npm install command
   - Provide basic React component
   - Explain configuration options
   - Link to full API docs

Example 2: Custom Playlists

User: "How do I create custom playlists with Shelby?"

1. Search: Grep "playlist" docs/ -i
2. Read: Playlist documentation
3. Answer:
   - Explain playlist API
   - Show creation example
   - Discuss management methods
   - Reference playlist options

Example 3: Streaming Configuration

User: "What streaming formats does Shelby support?"

1. Search: Grep "streaming|hls|dash" docs/
2. Read: Streaming guide
3. Answer:
   - List supported formats
   - Provide configuration examples
   - Explain adaptive bitrate
   - Show troubleshooting tips

Key Concepts to Reference

Media Player:

  • Player initialization
  • Configuration options
  • Event handling
  • Custom controls
  • Responsive design

Streaming:

  • HLS (HTTP Live Streaming)
  • DASH (Dynamic Adaptive Streaming)
  • Progressive download
  • Live streaming
  • DRM support (if available)

SDK Features:

  • TypeScript/JavaScript API
  • React/Vue components
  • Plugin system
  • Theming and styling
  • Analytics integration

CLI Tools:

  • Media processing
  • Transcoding
  • Playlist generation
  • Deployment helpers

TOON Format Notes

If documentation is in .toon format:

  • Most content is directly readable (tabular data)
  • Use TOON decoder for complex structures if needed:
    /Users/zach/Documents/claude-starter/.claude/skills/toon-formatter/bin/toon decode file.toon
    

Limitations

  • Only reference official Shelby documentation
  • If docs are incomplete, acknowledge gaps
  • For latest updates, suggest checking shelby.xyz or docs.shelby.xyz
  • Don't invent APIs or features not in docs

Response Style

  • Practical - developers want working code
  • Code-first - show examples immediately
  • Modern - use current JavaScript/TypeScript patterns
  • Cite sources - reference specific doc paths

Follow-up Suggestions

After answering, suggest:

  • Performance optimization
  • Error handling patterns
  • Testing strategies
  • Browser compatibility
  • Community resources or examples