tweet-reflect
Weekly strategy update — reweight content types from engagement data, prune accounts
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Weekly strategy update — reweight content types from engagement data, prune accounts
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Launch a Liquid Protocol token with a LiquidPresaleVault presale. STAKE MODE ONLY (policy 2026-06-12) — depositors lock DIEM and always get it back; allocation is lock-to-earn. One vault per launch, 10% of supply, 60d default lock.
Weekly audit of memory/goals.json — recompute milestone ETAs, self-funding ratio, mode consistency; report deltas and one recommendation to the creator
Proactive ambient check — surface anything worth attention
Analyze AUTONO's own performance and implement one high-impact improvement today
Safety net for Venice inference credits — if sDIEM is below stake_min_diem, queue a stake-diem intent for the gated executor
Run one AUTONOMOPOLY agent tick — claim fees, LP DIEM, LP range check + reposition, maintenance inference
| name | tweet-reflect |
| description | Weekly strategy update — reweight content types from engagement data, prune accounts |
| var | |
| tags | ["twitter","strategy"] |
Weekly strategy calibration based on real engagement data from the past 7 days.
Read memory/x-performance.jsonl. For snapshots in the last 30 days, group by content_type and compute:
median_likes, median_replies, median_repostsengagement_score = median_likes + median_replies * 2 + median_reposts * 1.5sample_count (how many tweets of this type)Content types with fewer than 3 samples: mark as insufficient_data, do not change their weight.
Rewrite the ## Content Type Weights section of memory/x-strategy.md with the computed scores. Normalise scores to sum to 1.0. Keep the prose sections intact — only update the weights table.
Format:
## Content Type Weights
_Updated: 2026-06-08 by tweet-reflect. Based on 14 engagement snapshots (last 30 days)._
| Type | Weight | Median engagement score | Sample count |
|------|--------|------------------------|--------------|
| on-chain-report | 0.35 | 6.2 | 5 |
| ecosystem-commentary | 0.28 | 4.8 | 4 |
| agent-philosophy | 0.22 | 3.9 | 3 |
| lp-update | 0.15 | 2.4 | 2 |
| reaction | — | — | insufficient_data (1 sample) |
If no performance data exists yet, write a note: "No data yet — equal weights applied by tweet-engage."
Read memory/x-performance.jsonl and memory/x-tweet-log.jsonl. Identify the top 3 tweets by engagement_score = likes + replies * 2 + reposts * 1.5 from the past 30 days. For each, fetch the tweet text from x-tweet-log.jsonl by tweet_id. Append to memory/x-promoted-candidates.jsonl (skip if tweet_id already present):
{"tweet_id":"...","content_type":"on-chain-report","engagement_score":8.5,"text":"[full tweet text]","nominated_at":"2026-06-08T09:00:00Z","status":"candidate"}
These are nomination-only — the operator manually moves approved candidates into identity/examples/promoted/.
Read memory/x-accounts.json. For each account:
engagement_score == 0 and added_at is more than 30 days ago: mark as status: inactiveengagement_scoreWrite updated memory/x-accounts.json.
Read memory/x-discovery-queue.jsonl (may not exist — skip silently if absent). For each entry, decide whether to add to x-accounts.json:
Mark processed entries with processed: true in the queue file.
Append to memory/logs/{today}.md:
tweet-reflect: top content type this week: TYPE (score X.X) | strategy updated | accounts pruned: N | new accounts added: N
Also set api_upgrade_ready: false in memory/x-strategy.md frontmatter unless tweet-broadcast or tweet-listen has had consecutive_failures >= 3 in memory/cron-state.json — if so, set api_upgrade_ready: true to signal the operator that the browser approach may need upgrading.