backup-files
Backup files to Backblaze B2 using rclone. Use when the user wants to back up files, sync files to the cloud, or mentions rclone/B2 backups.
What this skill does
# Backup Files
Backs up local files to Backblaze B2 using rclone.
## Arguments
- `$0`: (optional) local path to back up
- `$1`: (optional) destination subfolder within the bucket
## Default Bucket
The default destination bucket is `b2:czue-youtube-backups`.
## Important: --max-depth
By default, always use `--max-depth 1` to avoid recursing into subdirectories. rclone will crawl the entire directory tree otherwise, which can be very slow and pick up unrelated files. Only omit `--max-depth` if the user explicitly asks to include subdirectories.
## Workflow
1. **Resolve the source path**:
- If `$0` is provided, use it.
- Otherwise, use `AskUserQuestion` to ask what to back up, with these options:
- `~/Videos/` - Video files
- `~/Music/` - Music files
- `~/Documents/` - Documents
- Verify the source path exists before proceeding.
2. **Resolve the destination path**:
- If `$1` is provided, use `b2:czue-youtube-backups/$1` as the destination.
- Otherwise, use `AskUserQuestion` to ask for the destination subfolder within the bucket, suggesting a sensible default based on the source path (e.g. `~/Videos/` → `videos`, `~/Documents/` → `documents`).
3. **Determine depth**:
- Default to `--max-depth 1` (no subdirectory traversal).
- If the user explicitly requests recursive/subdirectory backup, omit `--max-depth`.
4. **Show what will be backed up**:
- Run `du -sh <source>` to show the total size.
- Run a dry run first so the user can see what will happen:
```bash
rclone copy <source> b2:czue-youtube-backups/<dest> --max-depth 1 --dry-run
```
- Show the user a summary and ask for confirmation before proceeding.
5. **Run the backup**:
```bash
rclone copy <source> b2:czue-youtube-backups/<dest> --max-depth 1 --progress --stats=5s
```
Run this in the foreground so the user can see progress.
6. **Report results**: Summarize what was backed up and the destination.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.