2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill glasses-to-social- _meta.json292 B
- SKILL.md3.7 KB
Overview
This skill turns photos taken with smart glasses into ready-to-publish social media posts. It monitors a Google Drive folder, analyzes new images with a vision model, drafts captions in the user's voice, and publishes after user approval. The pipeline supports manual checks or scheduled monitoring for hands-free content creation.
How this skill works
The agent watches a configured Google Drive folder for new images, downloads unseen files, and cross-references a processed list to avoid duplicates. Each new photo is analyzed by a vision AI to describe scene elements, detect text or people, and extract context. The agent drafts a concise first-person caption with suggested hashtags, sends the draft and image preview to the user for approval or edits, then publishes to the configured platform when approved and marks the photo as processed.
When to use it
- Setting up a glasses-to-social pipeline for hands-free content creation.
- Processing batches of smart-glasses photos into short social posts.
- Automating social posting for live events, conferences, or travel.
- Creating a reviewable stream of visual moments captured on wearable devices.
- Backing up and archiving glasses photos while generating captions.
Best practices
- Create a dedicated Google Drive folder and share with a consistent link for reliable syncing.
- Keep captions authentic and first-person; avoid over-editing the voice.
- Use a processed.json file to track handled images and prevent reposts.
- Tune default hashtags to your audience and add time-of-day context where relevant.
- Require user approval before posting to avoid accidental publishes and privacy issues.
Example use cases
- A conference attendee streams highlights from sessions and posts short reactions between talks.
- A field researcher captures daily observations and drafts captioned posts for a project account.
- A commuter shares interesting city scenes throughout the week without stopping to write captions.
- A creator archives glasses photos to Drive and auto-generates caption drafts for later scheduling.
FAQ
Any smart glasses that can sync photos to Google Drive will work; setup examples reference Meta Ray-Ban but the flow is generic.
How does the system avoid reposting the same photo?
Processed photos are logged in data/processed.json; new checks compare downloads against that list before analyzing or drafting.
Can posts be published automatically without approval?
Yes—autoPost can be enabled in configuration, but requiring manual confirmation is recommended for privacy and quality control.