Skip to content

ericrisco/rsc-harness / skills/init

Use when starting from nothing or pointing rsc at an existing project — the front door. First asks one question — technical terms or analogies (analogies by default) — then discovers what the user wants to build or govern (any stack, or a non-code harness: company/ops, research, knowledge, content), writes the profile to 02-DOCS, and installs the skills discovery justified. NOT the scaffolder (that is `harness`), NOT a stack skill.

FileKindSize
SKILL.mdskill md12.8 KB
evals/README.mdmarkdown2.9 KB
evals/cases.yamlconfig6.5 KB
references/accompaniment-and-profile.mdmarkdown6.0 KB
references/discovery.mdmarkdown5.8 KB
references/recommend-skills.mdmarkdown6.9 KB
scripts/verify.shexecutablescript4.3 KB

scripts/verify.sh

View on GitHub
#!/usr/bin/env bash
#
# verify.sh — bootstrap gate for the `init` skill.
#
# WHAT IT DOES (read-only; never edits or creates a file)
#   Static checks that Phase 1 (PROFILE) actually landed in the workspace:
#     1. 02-DOCS/wiki/harness/user-profile.md exists and carries a technical_level
#        line — the one dial (technical, or with analogies). The accompaniment dial
#        is retired: an old profile that still carries it is not flagged.
#     2. 02-DOCS/wiki/harness/decisions.md exists (append-only decisions log).
#     3. Root CLAUDE.md exists and its "## Knowledge map" section links the profile.
#   Everything is detect-or-skip: a missing workspace piece is a WARNING, never a
#   failure — `init` may simply not have run yet. The script never fails the build;
#   it only reports. (No --strict mode: this is a presence check, not a CI gate.)
#
# HOW TO RUN (inside YOUR workspace, not the skills repo)
#   ./verify.sh                 # check ./ for the profile + Knowledge-map link
#   ./verify.sh --path some/dir # check a different workspace root
#
# EXIT CODES
#   0  always, unless usage is wrong (this is a warn-only presence check)
#   2  bad usage
#
# Runs on stock macOS bash 3.2: no mapfile, no associative arrays, no process
# substitution; arrays avoided; everything POSIX-ish under `set -euo pipefail`.

set -euo pipefail

# --- color helpers (no escape codes when not a TTY) -------------------------
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; skip_count=0; warn_count=0

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

usage() {
  # print the header comment block (lines 2..24), stripping the leading "# "
  sed -n '2,24p' "$0" | sed 's/^# \{0,1\}//'
}

# --- arg parse --------------------------------------------------------------
ROOT="."
while [ $# -gt 0 ]; do
  case "$1" in
    --path)    ROOT="${2:?--path needs a value}"; shift 2 ;;
    -h|--help) usage; exit 0 ;;
    *) printf '%sUnknown argument: %s%s\n\n' "$RED" "$1" "$NC"; usage; exit 2 ;;
  esac
done

if [ ! -e "$ROOT" ]; then
  printf '%sPath not found: %s%s\n' "$RED" "$ROOT" "$NC"; exit 2
fi

PROFILE="$ROOT/02-DOCS/wiki/harness/user-profile.md"
DECISIONS="$ROOT/02-DOCS/wiki/harness/decisions.md"
CLAUDE_MD="$ROOT/CLAUDE.md"

# has <file> <pattern>: true if a non-empty file contains a case-insensitive match.
has() {
  [ -s "$1" ] || return 1
  grep -iq -e "$2" "$1" 2>/dev/null
}

printf 'Checking init PROFILE artifacts under: %s\n\n' "$ROOT"

# --- 1. user profile --------------------------------------------------------
if [ ! -s "$PROFILE" ]; then
  warn "no user profile at 02-DOCS/wiki/harness/user-profile.md — run init's PROFILE phase first"
else
  ok "user profile present: $PROFILE"
  if has "$PROFILE" 'technical_level'; then
    ok "profile records technical_level"
  else
    warn "profile is missing a technical_level line"
  fi
fi

# --- 2. decisions log -------------------------------------------------------
if [ ! -s "$DECISIONS" ]; then
  warn "no decisions log at 02-DOCS/wiki/harness/decisions.md — significant decisions should be appended here"
else
  ok "decisions log present: $DECISIONS"
fi

# --- 3. CLAUDE.md Knowledge map link ----------------------------------------
if [ ! -s "$CLAUDE_MD" ]; then
  warn "no root CLAUDE.md — init should create it with a '## Knowledge map' section"
else
  ok "root CLAUDE.md present"
  if has "$CLAUDE_MD" '## *Knowledge map'; then
    ok "CLAUDE.md has a '## Knowledge map' section"
    if has "$CLAUDE_MD" 'user-profile.md'; then
      ok "Knowledge map links the user profile"
    else
      warn "Knowledge map does not link 02-DOCS/wiki/harness/user-profile.md"
    fi
  else
    warn "CLAUDE.md has no '## Knowledge map' section linking the profile"
  fi
fi

# --- summary ----------------------------------------------------------------
printf '\nok=%d skip=%d warn=%d\n' "$ok_count" "$skip_count" "$warn_count"

cat <<'EOF'

Note: every finding is a presence WARNING, not a failure. If init has not run yet,
warnings are expected. Run init's PROFILE phase, then re-run this check.
EOF

exit 0
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall