← 返回 Skills 市场
ncreighton

Assetflow

作者 ncreighton · GitHub ↗ · v1.0.0 · MIT-0
macoslinuxwin32 ⚠ suspicious
119
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install assetflow
功能描述
Organize and store digital assets across cloud providers with automated workflows. Use when the user needs DAM integration, file organization, or asset metad...
使用说明 (SKILL.md)

\r \r

Overview\r

\r AssetFlow is a production-ready Digital Asset Management (DAM) orchestration skill that automates the organization, storage, and retrieval of digital assets across multiple cloud platforms and DAM systems. It eliminates manual file management overhead, ensures consistent metadata tagging, and integrates seamlessly with existing creative workflows.\r \r

Why AssetFlow Matters\r

\r Creative teams lose 30-40% of productivity managing dispersed assets across drives, cloud storage, and project folders. AssetFlow centralizes asset management with:\r \r

  • Automated Organization: Files are sorted by type, project, date, or custom taxonomy without manual intervention\r
  • Multi-Provider Integration: Works with AWS S3, Google Drive, Azure Blob Storage, Dropbox, Box, and native DAM platforms (Adobe Experience Manager, Widen Collective, Canto)\r
  • Intelligent Metadata: Auto-generates and applies tags, descriptions, and version tracking\r
  • Custom Workflows: Define organization rules for photos, video, design files, documents, and more\r
  • Access Control: Team-based permissions and approval workflows\r
  • Search & Discovery: AI-powered asset discovery by content, tags, or natural language queries\r \r ---\r \r

Quick Start\r

\r Try these example prompts immediately:\r \r

Example 1: Organize Marketing Assets\r

Organize all marketing materials from our Q4 campaign. \r
Automatically sort by asset type (images, videos, PDFs), \r
create project folders for each channel (social, email, web), \r
and tag with campaign name, brand guidelines compliance, and \r
expiration dates. Store in AWS S3 /marketing/Q4_2024 bucket.\r
```\r
\r
### Example 2: Set Up Photo Archive Workflow\r
```\r
Create an automated workflow for our photography team. \r
Ingest RAW files from Dropbox upload folder, auto-tag by \r
photographer and location metadata, generate thumbnails, \r
create proof sets, and move finalized images to archive \r
in Google Drive. Flag images that need licensing info.\r
```\r
\r
### Example 3: DAM System Sync\r
```\r
Sync all approved design files from our Figma workspace \r
to our Adobe Experience Manager DAM. Create asset collections \r
by brand, design system version, and usage rights. Auto-generate \r
previews and maintain version history. Alert team when assets \r
are updated or deprecated.\r
```\r
\r
### Example 4: Compliance & Retention\r
```\r
Implement automatic compliance workflow: tag all assets with \r
creation date, creator, usage rights, and expiration. Archive \r
assets older than 2 years to cold storage. Generate compliance \r
reports monthly. Flag any files missing required metadata.\r
```\r
\r
---\r
\r
## Capabilities\r
\r
### Automated Asset Organization\r
\r
- **Intelligent Sorting**: Classify files by type, date, project, or custom rules\r
- **Folder Structure Generation**: Create hierarchical organization matching your taxonomy\r
- **Batch Tagging**: Apply metadata at scale using pattern matching and AI\r
- **Version Control**: Track asset versions and maintain previous iterations\r
- **Duplicate Detection**: Identify and consolidate redundant assets\r
\r
### Multi-Provider Integration\r
\r
| Provider | Capability | Status |\r
|----------|-----------|--------|\r
| AWS S3 | Full read/write, lifecycle policies | ✅ Native |\r
| Google Drive | Folder management, sharing control | ✅ Native |\r
| Dropbox | Auto-ingest, selective sync | ✅ Native |\r
| Azure Blob | Archive storage, retention policies | ✅ Native |\r
| Adobe Experience Manager | DAM sync, metadata standards | ✅ API Integration |\r
| Canto | Asset collections, approval workflows | ✅ API Integration |\r
| Widen Collective | Brand management, usage rights | ✅ API Integration |\r
| Slack | Asset notifications, quick share | ✅ Webhook Integration |\r
\r
### Metadata & Searchability\r
\r
- **Auto-Generated Tags**: AI extracts subjects, objects, colors, and content type\r
- **Custom Metadata Schema**: Define fields (brand, campaign, usage rights, expiration)\r
- **Optical Character Recognition**: Extract text from images and documents\r
- **Face & Object Detection**: Automatically catalog people, locations, products\r
- **Natural Language Search**: "Find all winter campaign images with snow and people"\r
\r
### Workflow Automation\r
\r
- **Approval Chains**: Route assets requiring review to designated stakeholders\r
- **Scheduled Jobs**: Organize assets on a daily, weekly, or monthly cadence\r
- **Conditional Logic**: Apply different rules based on file type, size, or source\r
- **Notifications**: Alert teams via email or Slack when assets are organized, approved, or deprecated\r
- **Bulk Operations**: Process thousands of assets in a single batch\r
\r
### Access & Permissions\r
\r
- **Role-Based Access**: Assign viewer, editor, or admin permissions by team\r
- **Watermarking**: Automatically watermark preview assets\r
- **Download Tracking**: Log who accessed which assets and when\r
- **Expiring Links**: Create time-limited share links for external stakeholders\r
- **Audit Trails**: Full history of who modified or accessed each asset\r
\r
---\r
\r
## Configuration\r
\r
### Environment Variables (Required)\r
\r
```bash\r
# Primary DAM or storage provider authentication\r
ASSETFLOW_DAM_API_KEY="your-dam-api-key"\r
ASSETFLOW_STORAGE_PROVIDER="s3"  # Options: s3, gcs, azure, dropbox, box\r
ASSETFLOW_WORKSPACE_ID="workspace-12345"\r
\r
# AWS S3 (if using S3)\r
AWS_ACCESS_KEY_ID="your-aws-key"\r
AWS_SECRET_ACCESS_KEY="your-aws-secret"\r
AWS_REGION="us-east-1"\r
\r
# Google Cloud (if using Google Drive)\r
GOOGLE_APPLICATION_CREDENTIALS="/path/to/credentials.json"\r
\r
# Secondary integrations (optional)\r
ADOBE_XDM_API_KEY="adobe-api-key"\r
SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..."\r
```\r
\r
### Setup Instructions\r
\r
**Step 1: Choose Your Primary Provider**\r
```\r
Supported configurations:\r
- AWS S3 + Adobe Experience Manager\r
- Google Drive + Canto DAM\r
- Dropbox + Widen Collective\r
- Azure Blob Storage + custom metadata\r
```\r
\r
**Step 2: Define Asset Organization Schema**\r
```yaml\r
# Example taxonomy for marketing team\r
organization_rules:\r
  by_type:\r
    - images/\r
      - hero/\r
      - social/\r
      - email/\r
    - video/\r
      - shorts/\r
      - long-form/\r
    - documents/\r
      - brand-guidelines/\r
      - campaign-briefs/\r
  \r
  by_project:\r
    - [BRAND]_[QUARTER]_[CAMPAIGN_NAME]/\r
    - metadata_tags: [brand, quarter, campaign]\r
  \r
  retention_policy:\r
    approved_assets: "indefinite"\r
    drafts: "30 days"\r
    archival: "7 years cold storage"\r
```\r
\r
**Step 3: Configure Metadata Templates**\r
```yaml\r
# Required fields for all assets\r
metadata_template:\r
  core:\r
    - created_date (auto)\r
    - creator (auto)\r
    - asset_type (auto-detected)\r
    - usage_rights (required)\r
    - expiration_date (if applicable)\r
  \r
  custom:\r
    - brand\r
    - campaign\r
    - approved_by\r
    - version\r
    - file_format_quality\r
```\r
\r
**Step 4: Enable Integrations**\r
```\r
Slack notifications: Enable to post asset updates to team channels\r
Email digests: Weekly summary of new, modified, and archived assets\r
Webhook endpoints: For triggering external workflows\r
API access: For custom integrations with your tools\r
```\r
\r
---\r
\r
## Example Outputs\r
\r
### Output 1: Asset Organization Report\r
```\r
AssetFlow Organization Complete ✅\r
\r
📊 Summary:\r
- Files Processed: 4,892\r
- Files Organized: 4,721 (96.5%)\r
- Errors: 171 (flagged for review)\r
- Time: 23 minutes\r
\r
📁 Folder Structure Created:\r
marketing/\r
├── 2024/\r
│   ├── Q1_Launch/\r
│   │   ├── images/ (1,203 files)\r
│   │   ├── video/ (87 files)\r
│   │   └── documents/ (45 files)\r
│   └── Q2_Growth/\r
│       ├── images/ (892 files)\r
│       ├── video/ (156 files)\r
│       └── documents/ (234 files)\r
\r
🏷️ Metadata Applied:\r
- Tags: 14,832 (avg 3.2 per asset)\r
- Descriptions: 4,721 auto-generated\r
- Usage Rights: 4,703 classified\r
- Expiration Dates: 892 flagged\r
\r
⚠️ Requires Review:\r
- Missing Creator Info: 87 files\r
- Unclear Usage Rights: 56 files\r
- Potential Duplicates: 28 files\r
```\r
\r
### Output 2: DAM Sync Status\r
```\r
Adobe Experience Manager Sync: IN PROGRESS\r
\r
Files Synced: 1,234 / 1,456\r
Success Rate: 84.8%\r
\r
✅ Completed Syncs:\r
- Brand Assets (2024): 456 files\r
- Design System v3.2: 223 files\r
- Campaign Templates: 189 files\r
\r
🔄 In Progress:\r
- Video Archive: 156 files (12 minutes remaining)\r
- Historical Assets: 892 files (35 minutes remaining)\r
\r
⚠️ Failed Syncs (Requires Action):\r
- metadata_mismatch.zip: 12 files\r
  → Solution: Re-map custom metadata fields\r
\r
Next Steps:\r
1. Review failed sync report\r
2. Update Adobe XDM schema if needed\r
3. Retry failed files (automatic retry in 2 hours)\r
```\r
\r
### Output 3: Asset Search Result\r
```\r
🔍 Search Results: "winter campaign social media"\r
\r
Found 347 assets matching your criteria\r
\r
📸 Top Results:\r
\r
1. winter_campaign_instagram_1.jpg\r
   Size: 1.2 MB | Created: 2024-01-15\r
   Tags: winter, campaign, instagram, carousel\r
   Status: Approved ✅\r
   Downloads: 23\r
\r
2. winter_campaign_tiktok_15s.mp4\r
   Size: 45 MB | Created: 2024-01-18\r
   Tags: winter, campaign, tiktok, short-form\r
   Status: Approved ✅\r
   Downloads: 18\r
\r
3. winter_campaign_twitter_hero.png\r
   Size: 2.8 MB | Created: 2024-01-12\r
   Tags: winter, campaign, twitter, hero\r
   Status: In Review ⏳\r
   Downloads: 5\r
\r
[View all 347 results] [Save Search] [Create Collection]\r
```\r
\r
---\r
\r
## Tips & Best Practices\r
\r
### For Maximum Organization Efficiency\r
\r
1. **Establish Clear Naming Conventions Early**\r
   - Use consistent format: `[BRAND]_[DATE]_[PROJECT]_[TYPE]_[VERSION]`\r
   - Example: `ACME_2024-Q1_Newsletter_Header_v3.psd`\r
   - AssetFlow will auto-parse and apply metadata from filenames\r
\r
2. **Leverage Automated Workflows**\r
   - Set up ingest workflows for recurring uploads (e.g., daily photo drops)\r
   - Use conditional rules to route assets based on type or size\r
   - Schedule organization jobs during off-hours to avoid performance impact\r
\r
3. **Implement Approval Workflows Early**\r
   - Create approval chains for brand assets and customer-facing materials\r
   - Use Slack notifications to keep review cycles tight (target: 24-hour approval)\r
   - Archive rejected assets in a separate folder for reference\r
\r
4. **Maintain Metadata Discipline**\r
   - Require usage rights metadata before assets can be marked "approved"\r
   - Set expiration dates on trend-based or campaign-specific assets\r
   - Use tags for cross-project discovery (e.g., "client_XYZ", "summer_2024")\r
\r
5. **Monitor Storage & Costs**\r
   - Review storage usage monthly; archive cold assets to cheaper tier\r
   - Set up lifecycle policies to move assets to cold storage after 2+ years\r
   - Use preview versions to reduce bandwidth for large files\r
\r
6. **Optimize Search Experience**\r
   - Regularly review and refine your taxonomy based on search patterns\r
   - Create saved searches for frequently requested asset types\r
   - Use object detection tags to improve discoverability of visual content\r
\r
---\r
\r
## Safety & Guardrails\r
\r
### What AssetFlow Will NOT Do\r
\r
- **No Data Modification**: AssetFlow organizes and tags—it never alters file contents\r
- **No Unauthorized Sharing**: Respects original file permissions; cannot grant access users don't already have\r
- **No Sensitive Data Indexing**: Skips files containing PII, passwords, or encrypted content\r
- **No Creative Decisions**: Does not modify, edit, or reinterpret assets (e.g., no cropping, resizing, or color correction)\r
- **No Compliance Interpretation**: Does not automatically determine legal usage rights; flags for human review\r
\r
### Boundaries & Limitations\r
\r
| Limitation | Details | Mitigation |\r
|-----------|---------|-----------|\r
| File Size | Max individual file: 10 GB | Split large videos; compress RAW batches |\r
| API Rate Limits | 1,000 requests/minute per provider | Batch jobs during off-peak hours |\r
| Metadata Fields | Max 100 custom fields per asset | Use tagging system for additional classification |\r
| Search Indexing | Indexes file names, metadata, OCR; not full content | Use clear naming conventions |\r
| Concurrent Operations | Max 50 concurrent file operations | Monitor batch job queue |\r
\r
### Privacy & Compliance\r
\r
- **GDPR**: AssetFlow respects deletion requests; audit trails retained 90 days\r
- **SOC 2 Type II**: Encrypted in transit (TLS 1.3) and at rest (AES-256)\r
- **HIPAA**: Not suitable for PHI storage; consult compliance team before use\r
- **Data Residency**: Supports region-specific storage (EU, US, APAC)\r
\r
---\r
\r
## Troubleshooting\r
\r
### Common Issues & Solutions\r
\r
**Issue: "Authentication Failed" Error**\r
\r
```\r
Error: ASSETFLOW_DAM_API_KEY is invalid or expired\r
\r
Solution:\r
1. Verify API key in your provider dashboard (AWS/Google/Adobe)\r
2. Check key expiration date\r
3. Regenerate key if needed\r
4. Update environment variable: export ASSETFLOW_DAM_API_KEY="new-key"\r
5. Test connection: assetflow test-connection\r
```\r
\r
**Issue: Files Not Organizing Correctly**\r
\r
```\r
Problem: Assets ending up in wrong folders\r
\r
Troubleshooting:\r
1. Review your organization_rules YAML for typos or logic errors\r
2. Check file extensions match your rules (case-sensitive on Linux)\r
3. Verify metadata extraction is working:\r
   → assetflow debug --inspect-metadata [filename]\r
4. If using AI-based sorting, check confidence scores:\r
   → assetflow list-low-confidence --threshold 0.7\r
5. Manually correct folder assignments and retrain model\r
\r
Prevention: Start with simple rules (by type, then by date) \r
and gradually add complexity.\r
```\r
\r
**Issue: Slow Organization Performance**\r
\r
```\r
Symptom: Processing 10,000+ assets takes hours\r
\r
Optimization Steps:\r
1. Reduce concurrent operations: \r
   → assetflow organize --batch-size 25 --concurrency 10\r
2. Disable AI tagging for initial run (enable after):\r
   → assetflow organize --skip-ai-tags\r
3. Split into smaller batches by date or folder\r
4. Check for network latency to cloud storage:\r
   → ping your-bucket-region.amazonaws.com\r
5. Consider running during off-peak hours (2-6 AM)\r
\r
Expected Performance:\r
- Local SSD storage: ~1,000 files/minute\r
- Cloud storage (S3/GCS): ~200-400 files/minute\r
- With AI tagging: ~50-100 files/minute\r
```\r
\r
**Issue: Duplicate Assets Not Being Detected**\r
\r
```\r
Problem: Similar or identical files scattered across folders\r
\r
Debug:\r
1. Check duplicate detection is enabled:\r
   → assetflow config --show | grep duplicate\r
2. Review hash algorithm (MD5 for exact, perceptual for similar):\r
   → assetflow organize --duplicate-method perceptual\r
3. Adjust similarity threshold (0-100, default 85):\r
   → assetflow organize --similarity-
安全使用建议
This skill describes broad DAM, storage, and AI-driven features but only declares a few generic environment variables — ask the publisher for a complete list of required credentials and a clear description of what external APIs/endpoints the skill will call. Before installing, verify: (1) which provider credentials are required and whether you can supply least-privilege service accounts (e.g., S3 read/write limited to specific buckets, scoped OAuth tokens for Drive), (2) whether asset data or metadata will be sent to third-party endpoints (and which ones), (3) whether OCR/face-detection uses your cloud account or a third-party service, (4) how the skill requests credentials at runtime (env vars vs interactive prompts) and whether it stores them, and (5) test first in an isolated environment with non-sensitive assets. If the publisher cannot provide a full runtime spec (all env vars, endpoints, and credential handling), treat the skill as potentially unsafe and avoid granting broad credentials.
功能分析
Type: OpenClaw Skill Name: assetflow Version: 1.0.0 The skill bundle requests highly sensitive credentials, including AWS_SECRET_ACCESS_KEY, GOOGLE_APPLICATION_CREDENTIALS, and SLACK_WEBHOOK_URL, but provides no implementation code, relying entirely on the AI agent's interpretation of markdown instructions. There is a significant discrepancy between the documentation in SKILL.md, which references an 'assetflow' CLI tool for operations like 'test-connection' and 'debug', and the _meta.json/metadata which lists no required binaries. This creates a risk where the agent might attempt to install untrusted third-party packages (e.g., via pip) or execute unverified commands to satisfy the documented requirements, potentially leading to credential theft or supply chain exploitation.
能力评估
Purpose & Capability
The README claims native integrations with many providers (AWS S3, Google Drive, Azure, Dropbox, Adobe AEM, Slack, OCR/face detection, etc.) but the declared required env vars are just ASSETFLOW_DAM_API_KEY, ASSETFLOW_STORAGE_PROVIDER, and ASSETFLOW_WORKSPACE_ID. Real integrations normally require provider-specific credentials (AWS_ACCESS_KEY/SECRET, GCP OAuth tokens, Slack webhook token, Adobe API keys, vision/AI service credentials). This mismatch suggests the declared requirements are incomplete or the skill will request additional secrets at runtime.
Instruction Scope
SKILL.md is large and describes workflows that imply reading, moving, and uploading many user files and metadata across external services. As an instruction-only skill, its runtime behavior depends entirely on those prose directions; the visible instructions provide broad discretion (automated workflows, scheduled jobs, approvals, OCR, face detection). The doc likely expects the agent to access user assets and call external APIs; the SKILL.md does not clearly limit where credentials come from or explicitly enumerate all external endpoints or env vars it will access.
Install Mechanism
No install spec and no code files — lowest risk in terms of automatic code execution on install. All runtime behavior arises from the instruction text and the agent invoking APIs or user tools.
Credentials
The number and specificity of requested environment variables is small and generic for a skill that claims to integrate with many external services. The declared env vars do not cover provider-specific credentials or AI/vision services implied by features (OCR, face detection). This is disproportionate and leaves open how additional credentials will be supplied or used.
Persistence & Privilege
always is false and there are no requested config paths or claims to modify other skills or system-wide settings. Autonomous invocation is allowed (default), which is normal — but combined with the other concerns it increases potential impact if the skill requests or uses additional credentials at runtime.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install assetflow
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /assetflow 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial release of AssetFlow – an automated digital asset management workflow skill. - Automates organization, storage, and metadata tagging of digital assets across multiple cloud and DAM platforms. - Supports AWS S3, Google Drive, Azure Blob Storage, Dropbox, Box, and native DAM providers. - Includes intelligent asset sorting, batch tagging, version tracking, compliance, and approval workflows. - Integrates with Slack for notifications and Google Sheets for updates. - Configurable asset taxonomies, retention policies, and metadata templates. - Provides example prompts and setup instructions for quick onboarding.
元数据
Slug assetflow
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Assetflow 是什么?

Organize and store digital assets across cloud providers with automated workflows. Use when the user needs DAM integration, file organization, or asset metad... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 119 次。

如何安装 Assetflow?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install assetflow」即可一键安装,无需额外配置。

Assetflow 是免费的吗?

是的,Assetflow 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Assetflow 支持哪些平台?

Assetflow 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(macos, linux, win32)。

谁开发了 Assetflow?

由 ncreighton(@ncreighton)开发并维护,当前版本 v1.0.0。

💬 留言讨论