zero-yx/static_flow / skills/external-blog-repost-publisher
external-blog-repost-publisher
VerifiedRepost external blog articles into StaticFlow with style-aware translation, adaptive source normalization, image ingestion, and verified publish updates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| flows/publish-verify.md | markdown | 1.8 KB |
| flows/scope.md | markdown | 592 B |
| flows/source-normalization.md | markdown | 2.9 KB |
| flows/translation.md | markdown | 3.6 KB |
| references/sf-cli-troubleshooting.md | markdown | 2.1 KB |
references/sf-cli-troubleshooting.md
View on GitHub# `sf-cli` Troubleshooting for External Repost Publisher
Use this reference when publication/update commands fail in external repost workflow.
## 1) CLI not found
Symptom:
- `zsh: command not found: sf-cli`
Recovery:
1. Resolve executable in fallback order:
- `./target/release/sf-cli`
- `./target/debug/sf-cli`
- `../target/release/sf-cli`
- `sf-cli` from `PATH`
2. If missing, build:
- `cargo build -p sf-cli --release`
3. If the checkout is newer than the chosen binary, rebuild before use.
4. Do not prefer legacy `./bin/sf-cli` snapshots for storage-format-sensitive writes.
## 2) Wrong subcommand under `db`
Symptom:
- `error: unrecognized subcommand 'get-article'`
Reason:
- `get-article` is under `sf-cli api`, not `sf-cli db`.
Recovery:
1. Read article payload:
- `sf-cli api --db-path <db_path> get-article <id>`
2. Inspect table row:
- `sf-cli db --db-path <db_path> query-rows articles --where "id='<id>'" --format vertical --limit 1`
## 3) `db upsert-article` JSON shape mismatch
Symptoms:
- `Error: invalid article JSON`
- `invalid type: map, expected a string ...` (often `detailed_summary`)
- `missing field created_at`
Reason:
- `db upsert-article` expects `ArticleRecord` schema, not API response schema.
Recovery:
1. Normalize payload before upsert:
- `detailed_summary` must be stored as JSON string (not nested object),
- include required timestamps (`created_at`, `updated_at`).
2. Preserve original `created_at` for existing records.
3. If changing only a few columns, prefer `db update-rows` instead of full upsert.
## 4) Safe command selection by update scope
1. Narrow field patch (single/few columns):
- `sf-cli db update-rows ...`
2. Bilingual field patch from files:
- `sf-cli db update-article-bilingual ...`
3. Full overwrite/create with markdown source:
- `sf-cli write-article ...`
4. Full-row upsert:
- only when payload schema is fully normalized and timestamps are controlled.
## 5) Suggested diagnostics artifacts
Store in workspace (`/tmp/external_repost/<article_id>/`):
- `article_before.json`
- `article_after.json`
- `cli_diagnostics.log`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |