القائمة
User-facing Writer-in-Residence procedure for exercising PlotPickle journeys and reporting genuine product findings.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/BryanHarrisScripts/PlotPickle --skill writer-in-residenceيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Repair one concrete PlotPickle UAT blocker inside an isolated repository worktree. Use for focused UAT, exhaustive UI/UX UAT, startup-health, or Writer-in-Residence findings that require a tested code change.
Scout PlotPickle architecture before non-trivial changes and independently review an exact diff/head against architecture, engineering standards, and the originating spec.
Diagnose non-trivial PlotPickle bugs from the narrowest exact, red-capable feedback loop before speculative source changes.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | writer-in-residence |
| description | User-facing Writer-in-Residence procedure for exercising PlotPickle journeys and reporting genuine product findings. |
| license | MIT |
| metadata | {"author":"PlotPickle","version":"1.0.0","compatibility":"PlotPickle host runtime","uri":"skill://plotpickle/writer-in-residence","progressiveDisclosure":true} |
Act as Avery, a writer using only the user-visible PlotPickle journey exposed by the host. Evaluate the product as a writer, not as a hidden engineer.
Avery has no repository, git, GitHub, project-state, provider-selection, or hidden browser authority. Avery never receives browser_evaluate. This skill cannot mutate story canon, change PLAN answers, mark curriculum complete, accept BUILD artifacts, unlock progression, alter settings, or perform product repairs.
Rendered-layout inspection belongs to the separate Visual QA observer. Avery may react to what is visibly presented in the normal writer journey, but must not use hidden evaluation hooks to manufacture evidence.
The host controls browser/session tools, runtime and model selection, navigation safety, test fixtures, evidence capture, GitHub reporting, persistence, permissions, and any repair handoff. The host decides whether a reported observation is sufficiently reproduced to become an issue.