indranilbanerjee/neels-plugins / hermes/digital-marketing-pro/social/skills/index-assets
index-assets
VerifiedIndex the brand photo library with AI vision so assets are searchable and matchable. "catalogue our brand photos"
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.7 KB |
| storage-and-refresh.md | markdown | 1.7 KB |
storage-and-refresh.md
View on GitHub# index-assets — storage location and refresh behaviour
Supplementary to `SKILL.md`. Read this when the user asks where the index lives, why
`--refresh` did or did not ask for a source path, or the index is "missing" after a
host change. Everything below is read from `scripts/index_assets.py`.
## Where the index is written
`asset-index.json` is saved per brand:
1. `${CLAUDE_PLUGIN_DATA}/socialforge/brands/{brand}/asset-index.json` — when
`CLAUDE_PLUGIN_DATA` (or the Agent Plugins name `PLUGIN_DATA`) is set and the directory
exists. This survives sessions and plugin updates.
2. `~/socialforge-workspace/brands/{brand}/asset-index.json` — the fallback when neither
variable is set (or the directory does not exist).
If an index "disappeared", check which of the two roots the current host resolves before
re-indexing: a different host or a missing data variable lands in the other location.
## `--source` and `--refresh`
```
/socialforge:index-assets acme-corp --source /path/to/photos
/socialforge:index-assets acme-corp --source /path/to/photos --refresh (only new/changed files)
/socialforge:index-assets acme-corp --refresh (reuse the recorded source)
```
- The first index of a brand needs `--source`.
- A later run may omit `--source`: the script reuses the `source_path` recorded in the
previous `asset-index.json`, then the `path` / `url` in the brand's `asset-source.json`.
Only when neither exists does it stop with "`--source` is required".
- A Google Drive URL cannot be crawled by the script itself. Download the folder locally
and pass the local path, or (in Cowork) provide the folder contents through the Drive
integration.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |