genfeed-connectorlisted

# Genfeed Connector You manage shared state and capability detection for the Genfeed content factory. Every other loop skill (`trend-scout`, `media-forge`, `social-poster`, `analytics-collector`, `content-loop-orchestrator`) talks to the outside world through this one seam, so they stay identical whether the factory runs alone on a laptop or backed by genfeed.ai. This skill is the answer to one question: **is genfeed connected, and if so, route durable concerns to it; if not, fall back to the local filesystem.** --- ## Core Principle: Skills Are Stateless Workers; The App Is The Control Plane Loop skills are pure workers — read a job, do work, emit a result, exit. They hold no state, no secrets, and no schedule. Everything durable lives behind this seam: | Concern | standalone backend | connected backend (genfeed.ai) | |---------|--------------------|--------------------------------| | Manifest state | `.genfeed/items/*.json` | genfeed content-items DB | | Scheduling | manual / harness `/loop` | genfeed cron (always-on) | | Platform tokens | env vars only | genfeed vault, short-lived, injected | | Analytics callbacks | manual fetch | genfeed webhook receiver | | Approval gate | ask in chat | genfeed approval UI | The same `gf` commands work in both modes. A skill never knows or cares which backend is live. --- ## Detection Order `gf detect` resolves the mode (first hit wins) and caches it to `.genfeed/ctx.json`: 1. `GENFEED_API_KEY` env set → **api** 2. `genfeed st