Draft social posts and vendor feedback from a local model eval's conclusion pack, and publish only after the user approves the exact content.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use this after write-conclusion-pack has written report.md in a run directory.
The posts people share about local models answer "does this run on hardware like mine, and is it good enough to use". They lead with the machine, the model, the engine and quantization, and a concrete number; they show the recipe; and the ones that last are honest about limits. A surprising result on ordinary hardware travels further than a big number on expensive hardware.
Write in the user's own voice; read a few of their past posts first if an X account is connected. Plain sentences, no hype words, no emoji walls.
Save each to <run_dir>/posts/ and show them in the chat:
vendor-feedback.md, never published): what is worth promoting, what to fix with the evidence, and the follow-up experiments that confirmed it.Every number in a draft must appear in report.md. Do not add links you do not have; leave a placeholder.
If the review is paid or done in partnership with the model's vendor, the post must say so (#ad, "Sponsored", or "合作"). If you do not know, ask the user before drafting.
Posting goes through the user's connected accounts (X, LinkedIn, Reddit). holaOS blocks posting tools until the user approves the exact text, so:
ask_user_question.For platforms without a connected integration (for example Xiaohongshu), give the user the text and the image files to post themselves.
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.