webflow-automation
Automate Webflow CMS and Site Operations
Managing Webflow content manually is time-consuming and error-prone. This skill automates CMS operations, site publishing, and asset management through Rube MCP integration with Composio's Webflow toolkit.
Télécharger le ZIP du skill
Importer dans Claude
Allez dans Paramètres → Capacités → Skills → Importer un skill
Activez et commencez à utiliser
Tester
Utilisation de "webflow-automation". List Webflow sites
Résultat attendu:
Returns array of site objects with id, name, shortName, and customDomains. Example: [{id: "580e63fc8c9a982ac9b8b745", name: "My Site", shortName: "mysite", customDomains: ["example.com"]}]
Utilisation de "webflow-automation". Create CMS collection item
Résultat attendu:
Returns created item with _id, slug, created timestamp, and field data. Confirms item is staged and requires publishing to go live.
Audit de sécurité
Risque faibleStatic analyzer detected 158 external command patterns and 1 network reference. All external command detections are FALSE POSITIVES - they identify MCP tool names in documentation (e.g., WEBFLOW_LIST_WEBFLOW_SITES), not actual shell execution. The network finding references the legitimate Rube MCP endpoint (rube.app/mcp) required for skill operation. MD5 usage is for file integrity verification during S3 uploads, not cryptographic security. No malicious intent detected. Skill is safe for publication with minor documentation warnings about production actions.
Problèmes à risque faible (2)
Facteurs de risque
⚙️ Commandes externes (7)
🌐 Accès réseau (1)
Score de qualité
Ce que vous pouvez construire
Content Manager Bulk CMS Operations
Marketing teams can批量 create blog posts, update product listings, or manage team member directories by calling CMS tools in sequence with proper field slug resolution.
Developer Site Deployment Workflow
Developers can automate site publishing after staged changes, verify page structures via DOM inspection, and manage multiple site environments programmatically.
Ecommerce Order Monitoring
Store operators can retrieve order data, filter by status, and integrate order information into external reporting or fulfillment workflows.
Essayez ces prompts
List all Webflow sites I have access to and show me their IDs and names.
Show me all CMS collections for the site with ID [site_id] and explain what each collection contains.
Create a new blog post in the blog-posts collection with title "[Title]", slug "[post-slug]", and content "[content]". First verify the collection schema to get correct field slugs.
I need to add 3 new team members to our team collection. For each person, create a CMS item with their name, role, bio, and headshot. Then publish the site to make changes live. Confirm with me before publishing.
Bonnes pratiques
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas before any Webflow operations
- Call GET_COLLECTION to retrieve field slugs before creating or updating CMS items - never guess field names
- Confirm with users before executing PUBLISH_SITE or DELETE_COLLECTION_ITEM as these are irreversible production actions
Éviter
- Using field display names instead of slugs in CMS operations - always retrieve schema first
- Publishing without reviewing staged changes - PUBLISH_SITE deploys ALL pending changes
- Assuming all sites have ecommerce enabled - verify before calling order-related endpoints