Skip to main content

x-article-review

Review an article, title, thumbnail, and supporting files for factual support, reader usefulness, and consistency. Use for a publication-readiness check or a focused critique of a draft.

معلومات المصدر

المستودع
codejunkie99/x-article-skills
آخر نشاط في المصدر
٧ سبتمبر ٢٠٢٦ في ١٠:٠٧
لغة SKILL.md المكتشفة
الإنجليزية
النجوم
٢٦
التفرعات
٢

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

مستكشف الملفات
3 ملفات

عرض SKILL.md

SKILL.md
تعليمات المصدر · معاينة للقراءة فقط
name
x-article-review
description
Review an article, title, thumbnail, and supporting files for factual support, reader usefulness, and consistency. Use for a publication-readiness check or a focused critique of a draft.
# X Article Review Review the actual draft and requested assets. Use supplied evidence and verify changing claims through available primary sources where needed. Keep the review proportional to the task; a caption does not require an entire production audit. ## Ask concrete questions - Does the article deliver the title's promise, and does the thumbnail explain the same subject? - Can a reader identify the value in the opening? Does the TLDR give a useful shortcut? - Which claims are demonstrated, firsthand, attributed, estimated, or proposed? Are numbers attached to the correct person and time period? - Where would the intended reader get stuck? Are prerequisites, steps, exact locations, prompts, and expected results sufficient for the promised guide? - Does the visual remain readable at its intended size? Check labels, connectors, crop, hierarchy, and the specified ratio. - Do the files and links included in the handoff exist, open, and support the claims made about them? A style checker cannot prove originality or correctness. A model rating its own draft 10/10 is not a reliable stopping condition. A correlation in post analytics is not proof that a hook or thumbnail caused the result. ## Return useful findings Lead with material issues. For each, identify the passage or asset, why it matters, the evidence or missing evidence, and a concrete correction. Distinguish a required correction from a subjective preference. If a requested check could not be performed, state exactly what remains unverified. When asked to fix, make the authorized edits and check the changed areas. Stop when material issues are resolved; do not loop indefinitely or keep rewriting accepted content. If no material issues remain, say so briefly instead of inventing findings. Publication is a separate action. Do not post, send, or push solely because review was requested; if publication was already explicitly authorized, do not ask for the same permission again. See [review format](references/review-format.md) for a compact evidence-led report.
عرض على GitHub