Generate a weekly pregnancy update markdown file for a personal Obsidian vault. Use this skill whenever the user asks for 'this week's update', 'week X update', 'pregnancy update for week N', or any variation referring to weekly pregnancy info, fetal development, or guidance for an expecting couple. Trigger this even if the user just says 'let's do this week' in the context of a pregnancy. Produces a single markdown file with six sections — baby development, mum's body, partner support, what to say to her, to-dos, red flags — each with brief highlights and a collapsible detailed breakdown. Three audience modes are supported: combined (default, partner-facing, shared document), partner (rebalanced for the partner reading alone), and pregnant (second-person, addressed to the pregnant person) — pick one per generation from the user's wording or by asking. Synthesises NHS, Mayo Clinic, Cleveland Clinic, ACOG/RCOG, peer-reviewed maternal physiology research, Evidence Based Birth, and the couple's own curated research briefs on diet, exercise, and evidence-based birth interventions — explaining not just what is happening but why, with recurring emphasis on fetal brain and neurological development (neurogenesis, neuronal migration, synaptogenesis, myelination). Presents options, not prescriptions.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'foxtrotcharlie/family-skills (pregnancy-week-companion)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'foxtrotcharlie/family-skills (pregnancy-week-companion)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
3 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
24 findings · 10.6s
v0.3.74
12 findings · 1.7s
v0.1.0
0 findings · 3.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.2s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.3s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.3s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Flagged67 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 36 findings above stand exactly as their scanners reported them, at full severity.