Run any Skill in Manus with one click

cultureflare

Stars1

Forks0

UpdatedJune 22, 2026 at 18:48

Read-only visibility into CloudFlare state for the AgentCulture organization: zones, DNS records, Workers scripts and routes, Pages projects and deployments, plus a single-shot status digest. Use when: checking CloudFlare state, verifying DNS, inventorying Pages or Workers deployments, auditing before a cleanup, or the user says "cloudflare status", "cf-status", "check cloudflare", "list zones", "dns records", "pages deployments", "workers scripts", "workers routes", "cf-whoami", "cultureflare whoami", "cultureflare zones list", "inventory agentirc", "verify the cloudflare token".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

agentculture

agentculture/cultureflare

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

9 files

SKILL.md

readonly

More from this repository

same repository

recall

agentculture/cultureflare

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope cultureflare --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via t

2026-06-231

remember

agentculture/cultureflare

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope cultureflare --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save to

2026-06-231

cultureflare-write

agentculture/cultureflare

Write / edit / delete operations against CloudFlare state for the AgentCulture organization — create redirects, modify rules, delete resources. Use when: creating a CloudFlare redirect, adding a Single Redirect rule, editing / modifying CloudFlare state, deleting a Pages project / Worker / DNS record, or the user says "create redirect", "add cloudflare redirect", "edit cloudflare", "write cloudflare", "modify dns", "delete pages project", "cf-redirect-create", "cf-redirect", "cultureflare dns create". For **read-only** inventory (list zones / DNS / Workers / Pages, verify token), use the separate `cultureflare` skill — this skill never runs GET-only queries.

2026-06-231

cicd

agentculture/cultureflare

PR-review lane for cultureflare, layered on `agex pr`. Delegates lint / open / read / reply / delta to the agex CLI; adds two steward extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status, with non-zero exit on Sonar ERROR or unresolved threads). Use when: creating PRs in cultureflare, handling review feedback, polling CI status, or the user says "create PR", "review comments", "address feedback", "resolve threads", "/cicd". Vendored from steward 0.22.0; renamed from `pr-review` in steward 0.7.0; rebased on agex in 0.12.0.

2026-06-081

assign-to-workforce

agentculture/cultureflare

Fan out a converged devague plan's dependency waves to parallel agents in isolated git worktrees, one agent per task per wave, with TDD-gated merges by the main agent. Human gates: the exported spec, the implementation split plan (task map + per-task agent/model proposal + go/no-go), and the final PR. The devague CLI stays deterministic and non-orchestrating (#20) — it only *describes* the graph via `devague plan waves`; the operator (main agent) performs the fan-out. Use when the user says "assign to workforce", "fan out the plan", "parallel subagents", or after /spec-to-plan exports a plan. Authored and maintained in agentculture/devague (origin = devague); steward pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from steward like the other skills here.

2026-06-081

communicate

agentculture/cultureflare

Cross-repo + mesh communication from cultureflare: file tracked GitHub issues on sibling repos, comment on existing issues, fetch issues to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside cultureflare (a brief for a sibling-repo agent, a status ping for a Culture channel, or pulling an issue body + comments into context). Issue posts/comments auto-sign `- <nick> (Claude)`; mesh messages are unsigned (the IRC nick is the speaker). Not for in-cultureflare issues — use `gh issue create` or the `cicd` skill for those. Vendored from steward 0.12.0; GitHub issue I/O is agtag-backed since steward 0.11.0.

2026-05-141

name

cultureflare

description

cultureflare

Read-only skill for inspecting CloudFlare state. Every script is a thin wrapper around the CloudFlare REST API that renders an agent-readable markdown table (or key-value list for single-object responses) by default, and emits raw JSON with --json for bots and jq pipelines.

Read-only. For create / update / delete, use the companion cultureflare-write skill — it lives next to this one and shares _lib.sh via symlink.

How to invoke

Every verb available in Python is the preferred entry — faster, typed, tested. Bash scripts under scripts/ remain the fallback for verbs not yet ported; they continue to work unchanged. The Python CLI reads CLOUDFLARE_API_TOKEN (and, for account-scoped verbs, CLOUDFLARE_ACCOUNT_ID) from the environment only — it does not walk upward for a .env. Bash scripts still load .env from the repo root during coexistence.

Install: uv tool install cultureflare. Run cultureflare learn for the full agent prompt; cultureflare explain <path> for per-verb docs.

1. Pre-flight

Before running anything else, confirm credentials are wired:

cultureflare whoami

(Bash fallback: bash .claude/skills/cultureflare/scripts/cf-whoami.sh)

Expected output: a **CloudFlare token** section with the token id, status: active, not_before, and expires_on. If you see CLOUDFLARE_API_TOKEN not set, or if later scripts return code 10000 Authentication error, see docs/SETUP.md for the full token-creation walkthrough, the scope-to-script mapping, and common errors. cultureflare whoami does NOT list the token's granted scopes — /user/tokens/verify doesn't return them; consult the dashboard for scopes if needed.

2. Read recipes

Primary: installed Python CLI (v0.1.0: whoami, zones list). Bash fallback is in parentheses — still supported during the migration.

Question	Command
Is the token live?	`cultureflare whoami` (or `bash .claude/skills/cultureflare/scripts/cf-whoami.sh`)
What zones exist?	`cultureflare zones list` (or `bash .claude/skills/cultureflare/scripts/cf-zones.sh`)
What DNS records on `<zone>`?	`bash .claude/skills/cultureflare/scripts/cf-dns.sh <zone>` — (Python port pending)
What Workers scripts?	`bash .claude/skills/cultureflare/scripts/cf-workers.sh` — (Python port pending)
Routes across zones?	`bash .claude/skills/cultureflare/scripts/cf-workers-routes.sh`
Pages projects?	`bash .claude/skills/cultureflare/scripts/cf-pages.sh`
Full digest	`bash .claude/skills/cultureflare/scripts/cf-status.sh`

Every command accepts --json. Errors exit with codes 0 (success), 2 (env), 3 (auth), 4 (API). Run cultureflare learn for the full agent prompt, or cultureflare explain <path> for per-verb docs.

Prefer cf-status.sh for "what's the state?" questions. It runs every other read script in --json mode and composes one digest, so you get token + zones + Workers scripts + Workers routes + Pages projects in a single command (and therefore a single tool call) — no need to run five scripts, read each block, and stitch the summary together by hand.

3. Targeting culture.dev

The typical pattern for inspecting the primary zone:

# What's attached to culture.dev?
bash .claude/skills/cultureflare/scripts/cf-dns.sh culture.dev

# What Workers are behind culture.dev?
bash .claude/skills/cultureflare/scripts/cf-workers-routes.sh | grep culture.dev

# What Pages projects point at culture.dev?
bash .claude/skills/cultureflare/scripts/cf-pages.sh --json | jq '.result[] | select(.domains | any(test("culture.dev")))'

Scripts take zone/project names, not IDs — names are resolved internally.

4. Inventorying agentirc.dev before cleanup

agentirc.dev is the deprecated domain that's been folded into culture.dev/agentirc. The Pages deployment needs cleanup; this skill is the inventory tool before any removal.

# Confirm the Pages project still exists and find its exact name
bash .claude/skills/cultureflare/scripts/cf-pages.sh | grep -i agentirc

# Dump all deployments for that project
bash .claude/skills/cultureflare/scripts/cf-pages.sh <project-name>

# Check DNS records still attached to agentirc.dev
bash .claude/skills/cultureflare/scripts/cf-dns.sh agentirc.dev

# Check whether any Workers routes still point at agentirc.dev
bash .claude/skills/cultureflare/scripts/cf-workers-routes.sh | grep agentirc.dev

Save the outputs before the Phase 2 removal plan is written — they become the audit trail.

5. Output modes

Default is markdown:

List data → table (| COL | COL | + | --- | --- |) preceded by a ## <section> (<count>) heading.
Single-object data (only cultureflare whoami / cf-whoami today) → key-value list (- **key:** value).

--json bypasses all formatting:

# Pipe JSON into jq
bash .claude/skills/cultureflare/scripts/cf-zones.sh --json | jq '.result[].name'

# Check how many DNS records culture.dev has
bash .claude/skills/cultureflare/scripts/cf-dns.sh culture.dev --json | jq '.result | length'

Pagination: handled transparently for every list endpoint via cf_api_paginated in _lib.sh. You get every page concatenated into one .result array; override the per-page size by exporting CF_PAGE_SIZE in the environment of any script invocation, e.g. CF_PAGE_SIZE=25 bash .claude/skills/cultureflare/scripts/cf-zones.sh. The default is 50. cf-pages.sh pins it to 10 internally because the CloudFlare Pages list endpoint rejects per_page >= 11 with code 8000024; a user-supplied CF_PAGE_SIZE still wins if set.

6. What this skill does NOT do (yet)

Write operations. No create / update / delete. Added in a later phase with the same .claude/skills/cultureflare/scripts/ layout (new cf-*-create.sh / cf-*-delete.sh scripts).
Scope enumeration. cultureflare whoami / cf-whoami.sh reports token status and expiry but not granted scopes — the verify endpoint doesn't return them. Check the dashboard.
Account switching. One CLOUDFLARE_ACCOUNT_ID per .env; no multi-account support.
Live token testing in CI. The bats suite mocks curl via a PATH stub so tests run offline. The real token is only exercised manually or in a separately-configured workflow.

7. References

../cultureflare-write/references/cf-api-gotchas.md — consolidated CF API quirks. Several apply to reads too: the Pages per_page cap that cf-pages.sh has to work around (gotcha #1) and the zone-scope 10000 behavior (gotcha #6) both bite read-only callers.

8. Adding new read scripts

Follow the pattern every existing script uses:

Parse args with a for arg in "$@"; case "$arg" in ... esac loop. Support --json and -h/--help.
source "$(dirname "${BASH_SOURCE[0]}")/_lib.sh" — this loads .env, verifies CLOUDFLARE_API_TOKEN, and exposes cf_api, cf_api_paginated, cf_output, cf_output_kv, cf_require_account_id.
Call cf_require_account_id if the endpoint is account-scoped (/accounts/:id/...).
Fetch with cf_api_paginated for list endpoints; cf_api for single-object endpoints.
In md mode, emit a ## <section> (<count>)\n\n heading, then hand off to cf_output (table) or cf_output_kv (single object).
URL-encode any user-supplied argument before interpolation: jq -rn --arg v "$input" '$v|@uri'.
Add a fixture under tests/fixtures/, a bats file under tests/bats/, and cover at minimum: md rendering, --json passthrough, correct URL target, unknown-arg exit 2, API error exit 1.

Run bash tests/shellcheck.sh and bats tests/bats/ before committing.