THE DEFINITIVE ENTRY POINT for Fullstory implementation. Start here if you're unsure where to begin. This skill provides platform routing (Web vs Mobile), explains the skill architecture (Core → Meta → Industry → Framework), and guides you to the right resources for any Fullstory implementation question. Covers all platforms: Web (JavaScript/TypeScript), iOS (Swift/SwiftUI), Android (Kotlin/Compose), Flutter (Dart), and React Native.
🎯 START HERE: This is the definitive entry point for Fullstory implementation. If you're unsure where to begin, you're in the right place.
🤖 AGENT NOTE: Do NOT load all skills into context. If the user's request is unclear, ask what they want to focus on before loading additional skills. See "Key Takeaways for Agent" section below for loading strategy.
Every core skill follows a three-file pattern. You always start with SKILL.md for concepts, then go to the platform-specific file for implementation code.
┌─────────────────────────────────────────────────────────────────────────────┐
│ CORE SKILL FILE STRUCTURE │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ 📖 SKILL.md (START HERE) │
│ ├── Platform-agnostic concepts │
│ ├── API reference and parameters │
│ ├── Best practices and anti-patterns │
│ ├── When to use this API │
│ └── Links to SKILL-WEB.md and SKILL-MOBILE.md │
│ │
│ ┌─────────────────┴─────────────────┐ │
│ ▼ ▼ │
│ │
│ 🌐 SKILL-WEB.md 📱 SKILL-MOBILE.md │
│ JavaScript/TypeScript iOS (Swift/SwiftUI) │
│ React, Vue, Angular Android (Kotlin/Compose) │
│ Next.js, Svelte, etc. Flutter (Dart) │
│ Implementation code React Native │
│ Framework patterns Implementation code │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
fullstory-analytics-events/SKILL.md — Learn event naming, property types, rate limits, best practicesSKILL-WEB.md for JavaScript/TypeScript codeSKILL-MOBILE.md for iOS/Android/Flutter/React Native codeFor mobile implementations, the mobile-instrumentation-orchestrator helps you understand which skills to implement in what sequence:
Privacy Controls → User Identification → Page Properties → Analytics Events → Logging
The orchestrator doesn't replace reading SKILL.md files — it tells you which SKILL.md files to read and when, then routes to the appropriate SKILL-MOBILE.md sections for implementation.
The Fullstory Skills Repository (FSR) is organized in layers. Understanding this architecture helps you find the right guidance quickly.
┌─────────────────────────────────────────────────────────────────────────────┐
│ FULLSTORY SKILLS ARCHITECTURE (Start at Top, Work Down) │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌───────────────────────────────────────────────────────────────────────┐ │
│ │ CORE SKILLS (API Foundation) ← START HERE │ │
│ │ fullstory-identify-users, fullstory-analytics-events, etc. │ │
│ │ → Complete API reference and implementation guidance │ │
│ │ → SKILL.md: Platform-agnostic concepts and best practices │ │
│ │ → SKILL-WEB.md: JavaScript/TypeScript implementation │ │
│ │ → SKILL-MOBILE.md: iOS, Android, Flutter, React Native │ │
│ └───────────────────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ orchestrated by │
│ ┌───────────────────────────────────────────────────────────────────────┐ │
│ │ META SKILLS (Strategy Layer) │ │
│ │ fullstory-getting-started (YOU ARE HERE) │ │
│ │ fullstory-privacy-strategy, universal-data-scoping-and-decoration │ │
│ │ mobile-instrumentation-orchestrator │ │
│ │ → Expert guidance on using core APIs together effectively │ │
│ │ → Decision frameworks: what data, where, when │ │
│ │ → Implementation sequencing (which core skills in what order) │ │
│ └───────────────────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ guided by │
│ ┌───────────────────────────────────────────────────────────────────────┐ │
│ │ INDUSTRY SKILLS (Domain Expert Layer) │ │
│ │ fullstory-banking, fullstory-ecommerce, fullstory-healthcare, etc. │ │
│ │ → Industry-specific privacy requirements and regulations │ │
│ │ → Domain-specific data capture patterns │ │
│ │ → Compliance guidance (HIPAA, PCI, GLBA, GDPR) │ │
│ └───────────────────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ enhanced by │
│ ┌───────────────────────────────────────────────────────────────────────┐ │
│ │ FRAMEWORK SKILLS (Enhancement Layer) │ │
│ │ fullstory-stable-selectors, fullstory-test-automation │ │
│ │ → Cross-platform tooling: stable identifiers, test generation │ │
│ │ → Optional enhancements for automation and testing readiness │ │
│ └───────────────────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
| Layer | Purpose | When to Use | Entry Point | |-------|---------|-------------|-------------| | 1. Core | Complete Fullstory API expertise across web and mobile | Need to implement a specific API (identify, events, properties, etc.) | Always SKILL.md first, then SKILL-WEB.md or SKILL-MOBILE.md | | 2. Meta | Expert guidance on using APIs together | Planning implementation, deciding where data goes, sequencing | SKILL.md (orchestrates which core skills to use) | | 3. Industry | Domain-specific compliance and patterns | Working in regulated industries or need vertical-specific guidance | SKILL.md (references core skills for implementation) | | 4. Framework | Cross-platform tooling and automation | Need stable selectors for testing/AI, want test automation | SKILL.md, then SKILL-WEB.md or SKILL-MOBILE.md |
Each core skill provides complete guidance for one Fullstory API. Always start with SKILL.md for concepts, then read the platform-specific implementation file.
| Core Skill | API | Start Here | Then Implementation |
|------------|-----|------------|---------------------|
| fullstory-identify-users | User identification | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-anonymize-users | Session anonymization | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-user-properties | User attributes | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-page-properties | Page/screen context | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-element-properties | Interaction context | SKILL.md | SKILL-WEB.md, SKILL-IOS.md, SKILL-ANDROID.md, etc. |
| fullstory-analytics-events | Custom events | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-privacy-controls | Mask/exclude elements | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-user-consent | GDPR/CCPA consent | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-capture-control | Pause/resume | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-observe-callbacks | Lifecycle hooks | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-logging | Session logging | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| fullstory-async-methods | Promise-based APIs | SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
Meta skills don't replace core skills — they help you use core skills effectively.
| Meta Skill | Purpose |
|------------|---------|
| fullstory-getting-started | Entry point — skill architecture, navigation, web quick start |
| mobile-instrumentation-orchestrator | Mobile sequencing — which core skills to implement and in what order (routes to SKILL-MOBILE.md files) |
| fullstory-privacy-strategy | Privacy expert — what to capture, mask, exclude, hash (works with fullstory-privacy-controls) |
| universal-data-scoping-and-decoration | Data placement expert — user vs page vs element vs event (works with property skills) |
| Industry Skill | Regulations | Key Concerns |
|----------------|-------------|--------------|
| fullstory-banking | PCI, GLBA, SOX | Financial data exclusion, amount ranges |
| fullstory-healthcare | HIPAA, HITECH | PHI exclusion, BAA requirements |
| fullstory-ecommerce | PCI, CCPA, GDPR | Conversion tracking, payment exclusion |
| fullstory-gaming | Gaming licenses, AML | Responsible gaming, wager exclusion |
| fullstory-saas | SOC 2, GDPR | Feature adoption, customer data |
| fullstory-travel | PCI, GDPR | Booking flows, ID exclusion |
| fullstory-media-entertainment | COPPA, GDPR | Engagement, children's privacy |
| Framework Skill | Purpose |
|-----------------|---------|
| fullstory-stable-selectors | Stable identifiers using the Data Attributes Guide convention (data-component, data-id, data-section, data-position, data-state). Supports Framework approach (shared components) and Individual Element decoration — agents should ask users which approach they prefer |
| fullstory-test-automation | Generate test automation from decorated codebases |
| Question | Go To | Then |
|----------|-------|------|
| "How do I implement user identification?" | fullstory-identify-users/SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| "How do I track events?" | fullstory-analytics-events/SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| "How do I protect sensitive data?" | fullstory-privacy-controls/SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| "What data should I capture vs mask vs exclude?" | fullstory-privacy-strategy/SKILL.md | (strategy, then core skills) |
| "Should this be a user property, page property, or event?" | universal-data-scoping-and-decoration/SKILL.md | (strategy, then core skills) |
| "What order should I implement mobile APIs?" | mobile-instrumentation-orchestrator/SKILL.md | (sequencing, routes to SKILL-MOBILE.md) |
| "I'm in healthcare/banking/etc — what rules apply?" | fullstory-{industry}/SKILL.md | (guidance, references core skills) |
| "How do I add stable selectors for testing/AI?" | fullstory-stable-selectors/SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
| "How do I generate tests from my decorated codebase?" | fullstory-test-automation/SKILL.md | SKILL-WEB.md or SKILL-MOBILE.md |
For mobile SDK installation and initial setup, Fullstory provides comprehensive official guides. Use these for SDK setup, then return to the core skills' SKILL-MOBILE.md files for API usage guidance.
| Platform | Installation Guide | What It Covers | |----------|-------------------|----------------| | Android (Kotlin) | Getting Started with Android Data Capture | Comprehensive Android setup: Gradle, initialization, ProGuard, configuration | | + Jetpack Compose | Getting Started with Jetpack Compose | Additional Compose-specific setup (use with Android guide above) | | iOS (UIKit/Swift) | Getting Started with iOS Data Capture | Comprehensive iOS setup: CocoaPods/SPM, initialization, Info.plist | | + SwiftUI | Integrating Fullstory into a SwiftUI App | Additional SwiftUI-specific setup (use with iOS guide above) | | Flutter | Getting Started with Flutter Mobile Apps | pub.dev setup, Dart initialization | | React Native | Getting Started with React Native Capture | npm/yarn setup, native linking | | Cordova/Capacitor | Getting Started with Cordova or Capacitor | Plugin installation, hybrid app setup |
For Android, you can use the in-repo setup guide so the AI companion can apply the changes for you:
project/build.gradle (or settings.gradle), app/build.gradle, and initialization code as needed.After the agent applies the edits, continue with the core skills’ SKILL-MOBILE.md files for API usage (identify, events, properties, privacy).
For iOS, you can use the in-repo setup guide so the AI companion can apply the changes for you:
Info.plist.After the agent applies the edits, continue with the core skills' SKILL-MOBILE.md files for API usage (identify, events, properties, privacy).
For Flutter, you can use the in-repo setup guide so the AI companion can apply the changes for you:
flutter pub add fullstory_flutter, then modify your Dart entry-point (runApp → runFullstoryApp, etc.) with the required import.After the agent applies the edits, continue with the core skills' SKILL-FLUTTER.md files for API usage (identify, events, properties, privacy).
For React Native, you can use the in-repo setup guide so the AI companion can apply the changes for you:
After the agent applies the edits, continue with the core skills' SKILL-REACT-NATIVE.md files for API usage (identify, events, properties, privacy).
Once the SDK is installed and capturing data:
fullstory-identify-users/SKILL.md)mobile-instrumentation-orchestrator/SKILL.md for recommended implementation orderNote: The official guides above cover SDK installation. The skills repository covers API usage — how to identify users, track events, set properties, handle privacy, etc.
Note: This section provides a web quick start overview. For complete API guidance, always read the relevant core skill's SKILL.md first, then its SKILL-WEB.md for detailed implementation code.
| API | Method | Purpose | Core Skill |
|-----|--------|---------|------------|
| Identity | FS('setIdentity', { uid, properties }) | Identify known users | fullstory-identify-users |
| Anonymize | FS('setIdentity', { anonymous: true }) | End identified session | fullstory-anonymize-users |
| User Properties | FS('setProperties', { type: 'user', ... }) | Update user attributes | fullstory-user-properties |
| Page Properties | FS('setProperties', { type: 'page', ... }) | Set page context | fullstory-page-properties |
| Element Properties | data-fs-* attributes | Capture interaction context | fullstory-element-properties |
| Events | FS('trackEvent', { name, properties }) | Track discrete actions | fullstory-analytics-events |
| Observers | FS('observe', { type, callback }) | React to FS lifecycle | fullstory-observe-callbacks |
| Logging | FS('log', { level, msg }) | Add logs to session | fullstory-logging |
| Consent | FS('setIdentity', { consent: bool }) | Control capture consent | fullstory-user-consent |
| Capture Control | FS('shutdown') / FS('restart') | Pause/resume capture | fullstory-capture-control |
| Async Methods | FS('*Async') variants | Promise-based API calls | fullstory-async-methods |
┌─────────────────────────────────────────────────────────────────────┐
│ FULLSTORY BROWSER API v2 │
├─────────────────────────────────────────────────────────────────────┤
│ IDENTITY & USER │
│ ├── setIdentity (uid) - Identify users │
│ ├── setIdentity (anonymous) - Anonymize users │
│ ├── setIdentity (consent) - Manage consent │
│ └── setProperties (user) - Update user attributes │
├─────────────────────────────────────────────────────────────────────┤
│ CONTEXT & PROPERTIES │
│ ├── setProperties (page) - Page-level context │
│ └── Element Properties - Interaction-level context │
├─────────────────────────────────────────────────────────────────────┤
│ EVENTS & ACTIONS │
│ └── trackEvent - Discrete business events │
├─────────────────────────────────────────────────────────────────────┤
│ PRIVACY & CONTROL │
│ ├── fs-exclude / fs-mask - Element privacy classes │
│ ├── shutdown / restart - Capture control │
│ └── consent - User consent management │
├─────────────────────────────────────────────────────────────────────┤
│ LIFECYCLE & UTILITIES │
│ ├── observe - Lifecycle callbacks │
│ ├── log - Session logging │
│ ├── getSession - Get session URL │
│ └── *Async variants - Promise-based methods │
└─────────────────────────────────────────────────────────────────────┘
For snippet installation and configuration, see the official Fullstory documentation:
Getting Started with Web — Comprehensive guide covering:
@fullstory/browser, Google Tag Manager, Segment, Tealium)_fs_org, _fs_namespace, _fs_capture_on_startup)Once the snippet is installed and capturing data:
fullstory-identify-users/SKILL.md)Note: The official guide covers snippet installation. The skills repository covers API usage — how to identify users, track events, set properties, handle privacy, etc.
Phase 1: Foundation
├── 1. Install snippet
├── 2. Implement privacy controls (fs-exclude, fs-mask)
├── 3. Implement user identification (login flow)
├── 4. Implement anonymization (logout flow)
└── 5. Set up basic page properties (pageName)
Phase 2: Context
├── 6. Add user properties (plan, role, company)
├── 7. Enhance page properties (search terms, filters)
└── 8. Add element properties (product IDs, positions)
Phase 3: Events
├── 9. Implement key business events
├── 10. Add funnel tracking
└── 11. Add feature usage tracking
Phase 4: Advanced
├── 12. Set up observers for session URL
├── 13. Implement consent flows (if GDPR required)
├── 14. Add error logging
└── 15. Implement capture control (if needed)
Phase 5: Enhancement (Optional)
├── 16. Add stable selectors (fullstory-stable-selectors)
└── 17. Generate test automation (fullstory-test-autom
<!-- Content truncated for initial SEO render. Open the source file tab for the full file. -->
npx skills add fullstorydev/fullstory-getting-started下载完整 Skill 目录，包含 SKILL.md 及所有相关文件
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer