church-social-post Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• SKILL.md references the pastor-foundation and pastor-setup skills and a fixed ~/.claude/pastor-profile.md path, but does not explain how to verify or install those dependencies, so the skill may not be self-contained.
• Financial research output is not financial advice; require human review before any live investment decision
• The provided SKILL.md excerpt ends mid-sentence in the Anti-Patterns section; if this is the complete file, it is incomplete.
• There are no explicit limitations or safety boundaries for sensitive content such as privacy/consent for testimonies and photos, minors, crisis communications, or confidential church member information.