Install any skill in seconds. Free to start, no credit card required.
Get Started Free →miantiao-me/publish-weekly
使用 Payload REST API 将周刊写入 CMS(发布为草稿),通过 users API Key 认证。
Passed 12 of 20 test cases with the skill, and 5 of 20 without it.
and 7 more in the full report
9 fixed5 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact string title should be passed in the Bark notification JSON payload when draft issue Y26W26 is successfully saved?
| Checked | Without skill | With skill |
|---|---|---|
| Sets Bark notification title field to Y26W26|周刊草稿已生成. | Missed | Passed |
The instructions your model reads when the skill loads.
此技能用于将本地生成的周刊 Markdown 文件发布到 Payload CMS 的 weekly 集合中,并保持为 草稿(status: draft)。
PAYLOAD_API_KEY:来自 Payload users 集合为某个用户生成的 API Key。PAYLOAD_BASE_URL(推荐):Payload/Next.js 服务的公开地址(例如 http://localhost:3000)。BARK_PUSH_URL(可选):完整的 Bark 推送端点(例如 https://push.example.com/push/token/);未配置时跳过通知。从 /weekly 命令的参数块中获取:
week_id:如 Y26W12(写入 issueNumber)title:写入 titlefilename:周刊 Markdown 文件名(从工作目录读取该文件内容,写入 content)current_date:写入 publishDate(ISO 日期字符串)可选:
summary:周刊描述/摘要(写入 summary)。若未提供则从 content 提炼。tags:标签(字符串数组,例如 ["模型", "工具"])。写入 tags 数组字段。links:链接列表(对象数组,形如 [{ label, url }]),写入 links。weeklyGET {BASE_URL}/api/weekly?where[issueNumber][equals]={week_id}&limit=1POST {BASE_URL}/api/weeklyPATCH {BASE_URL}/api/weekly/{id}必须使用 Payload 的 API Key 认证头:
Authorization: users API-Key {PAYLOAD_API_KEY}
Content-Type: application/json
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.