call-recap vs writing-plans

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

Metriccall-recapSkill writing-plansSkill

Type: call-recapSkill; writing-plansSkill
Category: call-recapWriting; writing-plansWriting
GitHub stars: call-recap0; writing-plans0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: call-recapNot yet assessed; writing-plansNot yet assessed
Community rating: call-recapNo reviews yet; writing-plansNo reviews yet
Last commit: call-recapUnknown; writing-plansUnknown
Licence: call-recapNone declared; writing-plansNone declared
Official: call-recapNo; writing-plansNo
Source: call-recap Repository; writing-plans Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.