# geoflow-content-automation

A skill that walks your agent through GEOFlow: AI article generation, task scheduling, review and publishing via CLI, REST API and Docker. Useful when the content pipeline runs on PHP and PostgreSQL.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 442 installs · ★ 88
- Author: reason-machines
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/reason-machines/trending-skills/tree/HEAD/skills/geoflow-content-automation/SKILL.md
- Updated: 2026-10-09
- HTML: https://affpapa.org/en/nevibecode/skills/geoflow-content-automation

## What it does

The skill covers the whole GEOFlow chain: model setup, materials, task creation, draft, review, publish. It knows the CLI at `php bin/geoflow` and `php bin/cron.php`, the `/api/v1` endpoints behind a Bearer token, and PHP snippets that use `includes/db_support.php` with `get_db_connection()`. Ask the agent to create a task, check the `job_queue` table, or move an article out of draft.

Deployment goes through Docker Compose: `web` and `postgres` always, plus `scheduler` and `worker` under the `scheduler` profile. There is a local route too — `php -S localhost:8080 router.php`. That one needs PHP 7.4+ with `pdo_pgsql` and `curl`, and a running PostgreSQL. Miss any of those and the server will not come up, so check the environment first.

On first boot the admin panel at `/geo_admin/` accepts `admin` and `admin888`. Change both right away and regenerate `APP_SECRET_KEY` with `openssl rand -hex 32`; leaving the defaults on a public host hands the panel to anyone. Any OpenAI-compatible API works as a model — set the Base URL, Model ID and key.

## Requirements
- Works with: PostgreSQL

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill geoflow-content-automation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/geoflow-content-automation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/geoflow-content-automation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill geoflow-content-automation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/geoflow-content-automation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill geoflow-content-automation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/geoflow-content-automation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install reason-machines/trending-skills geoflow-content-automation
```

2. **Manually: put the files in place**
- File: `.github/skills/geoflow-content-automation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill geoflow-content-automation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/reason-machines/trending-skills --path skills/geoflow-content-automation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/geoflow-content-automation/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add reason-machines/trending-skills --skill geoflow-content-automation -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/reason-machines/trending-skills/tree/HEAD/skills/geoflow-content-automation/SKILL.md

## When to use it
- wire up an article pipeline from task to publish
- connect an OpenAI-compatible model to GEOFlow
- queue a generation task from the CLI or REST API
- push a draft through review and publish it
- debug a stuck worker or scheduler

## Example prompts
- Bring up GEOFlow with Docker Compose and the scheduler profile, then tail the worker logs
- Create a GEOFlow task with `php bin/geoflow task:create` and set publish mode to draft
- Check `/api/v1/jobs?status=pending` and tell me what is stuck in the queue

## Similar
- [seo-audit](https://affpapa.org/en/nevibecode/skills/coreyhaines31-seo-audit.md) — skill · 237600 installs
- [brand](https://affpapa.org/en/nevibecode/skills/brand.md) — skill · 39900 installs
- [banner-design](https://affpapa.org/en/nevibecode/skills/banner-design.md) — skill · 39500 installs
- [marketing-psychology](https://affpapa.org/en/nevibecode/skills/coreyhaines31-marketing-psychology.md) — skill · 164600 installs
- [content-strategy](https://affpapa.org/en/nevibecode/skills/coreyhaines31-content-strategy.md) — skill · 164000 installs
- [ai-seo](https://affpapa.org/en/nevibecode/skills/ai-seo.md) — skill · 150800 installs

From the same set: [reason-machines/trending-skills](https://affpapa.org/en/nevibecode/by/reason-machines/trending-skills.md) — 186 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md