القائمة
Reply to a public review so the next reader is reassured, not the reviewer argued with.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/vstorm-co/agenticos --skill review-responseيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | Review response |
| description | Reply to a public review so the next reader is reassured, not the reviewer argued with. |
| category | marketing |
The audience is the next reader, not the reviewer. That single fact decides the tone.
Acknowledge the specific thing · say what happened if you know · say what you are doing about it · move the detail off the public thread with a real contact route. Four sentences is usually enough.
Never dispute the facts in public, even when they are wrong. "That is not what our records show" reads as combative to everybody except the person who wrote it. Acknowledge, resolve privately, and come back to update the thread if it is resolved.
Reply to the specific detail they praised. A generic thank-you on fifty reviews reads as automation and devalues all of them.
Sign with a name and a role. An unsigned corporate reply persuades nobody.
Offer compensation in public, ask for the review to be removed, or reply to a one-star review within minutes of it landing — it reads as reflex.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.