Skip to content

ericrisco/rsc-harness / skills/medium-strategy

medium-strategy

Verified

Use when planning Medium as a growth and revenue system over months rather than one post — the Partner Program, solo profile versus starting or pitching a publication, engineering for Boost and the distribution tiers, tag and topic choices for reach, and a canonical cross-posting plan, read from and written back to the wiki so each session compounds. NOT writing the article's hook, structure or prose (that is `medium-writing`), NOT the mechanical format-and-submit step (that is `medium-publishing`).

FileKindSize
SKILL.mdskill md14.3 KB
evals/README.mdmarkdown780 B
evals/cases.yamlconfig3.5 KB
references/distribution-and-boost.mdmarkdown4.2 KB
references/wiki-records.mdmarkdown5.1 KB
scripts/verify.shexecutablescript3.8 KB

scripts/verify.sh

View on GitHub
#!/usr/bin/env bash
#
# verify.sh — structural lint for a medium-strategy wiki under 02-DOCS/wiki/medium/.
#
# WHAT IT DOES (read-only; never edits a file)
#   Static, network-free checks on the decision records the skill writes back.
#     1. The target directory exists.
#     2. At least one decision record is present: a file under decisions/*.md
#        OR a running decisions.md log at the target root.
#     3. Each decision record carries the three required signals:
#          - a date              (a YYYY-MM-DD anywhere in the file)
#          - a Decision: line     (the concrete choice)
#          - a named metric/bet   (a "Bets on metric:" / "metric" / "bet" field)
#        A record missing the metric/bet field is a HARD FAILURE — a decision
#        with no metric is an opinion, not a checkable bet.
#
#   Missing date or Decision line is also a hard failure. A missing/empty target
#   (a fresh account with no wiki yet) is reported and exits 0 — no false failure.
#   Pure bash + grep, no dependencies. It is a lint, not a strategy oracle.
#
# HOW TO RUN
#   ./verify.sh 02-DOCS/wiki/medium/    # lint an account's strategy wiki
#   ./verify.sh                         # no target -> nothing to check, exit 0
#
# EXIT CODES
#   0  clean, or nothing to check
#   1  a hard structural failure
#   2  bad usage
#
# Runs on stock macOS bash 3.2.

set -euo pipefail

if [ -t 1 ]; then
  RED=$'\033[31m'; GREEN=$'\033[32m'; YELLOW=$'\033[33m'; NC=$'\033[0m'
else
  RED=''; GREEN=''; YELLOW=''; NC=''
fi

ok_count=0; warn_count=0; fail_count=0
ok()   { printf '%s[ ok ]%s %s\n' "$GREEN"  "$NC" "$*"; ok_count=$((ok_count + 1)); }
warn() { printf '%s[warn]%s %s\n' "$YELLOW" "$NC" "$*"; warn_count=$((warn_count + 1)); }
fail() { printf '%s[fail]%s %s\n' "$RED"    "$NC" "$*"; fail_count=$((fail_count + 1)); }

usage() { sed -n '2,34p' "$0" | sed 's/^# \{0,1\}//'; }

summary_exit() {
  printf '\nok=%d warn=%d fail=%d\n' "$ok_count" "$warn_count" "$fail_count"
  [ "$fail_count" -gt 0 ] && exit 1
  exit 0
}

# --- arg parse --------------------------------------------------------------
TARGET=""
while [ $# -gt 0 ]; do
  case "$1" in
    -h|--help) usage; exit 0 ;;
    -*) printf 'unknown flag: %s\n' "$1" >&2; usage >&2; exit 2 ;;
    *) TARGET="$1"; shift ;;
  esac
done

# No target, or missing dir -> nothing to check, clean exit (no false fail).
if [ -z "$TARGET" ]; then
  ok "no wiki path given — nothing to lint"
  summary_exit
fi
if [ ! -d "$TARGET" ]; then
  warn "directory not found: $TARGET — nothing to lint (fresh account?)"
  summary_exit
fi
ok "wiki directory exists: $TARGET"

# --- collect decision records ----------------------------------------------
# Per-decision files under decisions/, plus an optional running decisions.md log.
RECORDS=""
if [ -d "$TARGET/decisions" ]; then
  for f in "$TARGET"/decisions/*.md; do
    [ -f "$f" ] && RECORDS="$RECORDS$f
"
  done
fi
[ -f "$TARGET/decisions.md" ] && RECORDS="$RECORDS$TARGET/decisions.md
"

# Trim blank lines / handle empty.
RECORDS="$(printf '%s' "$RECORDS" | sed '/^$/d')"

if [ -z "$RECORDS" ]; then
  warn "no decision records yet (decisions/*.md or decisions.md) — nothing to lint"
  summary_exit
fi

# --- per-record structural checks ------------------------------------------
DATE_RE='[0-9]{4}-[0-9]{2}-[0-9]{2}'

while IFS= read -r rec; do
  [ -z "$rec" ] && continue
  if [ ! -s "$rec" ]; then
    fail "$rec: empty record"
    continue
  fi

  miss=""
  grep -Eq  "$DATE_RE"                       "$rec" || miss="$miss date"
  grep -Eiq '^[[:space:]-]*Decision:'        "$rec" || miss="$miss decision-line"
  grep -Eiq '(bets on metric:|metric|bet:)'  "$rec" || miss="$miss metric/bet"

  if [ -n "$miss" ]; then
    fail "$rec: missing required field(s):$miss"
  else
    ok "$rec: date + decision + metric present"
  fi
done <<EOF
$RECORDS
EOF

summary_exit
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall