{"id":18289,"plugin_id":"plugins_6a88cdd968088191b7a22c9e92cbb5ba","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:46.121Z","digest":"1bbe96a7620ca91101c46ba4911cf3dde601da67e27a7a957b7204d3354caedc","against":null,"payload":{"name":"course-redesign-research","description":"Conduct verification-first educational and disciplinary research for an approved course-redesign focus, with source, quotation, date, rights, and uncertainty controls. Use for fact-checking, literature review, evidence synthesis, source verification, citations, or Scite/browser research inside a course-redesign run.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":253}],"skill_md_contents":"---\nname: course-redesign-research\ndescription: Conduct verification-first educational and disciplinary research for an approved course-redesign focus, with source, quotation, date, rights, and uncertainty controls. Use for fact-checking, literature review, evidence synthesis, source verification, citations, or Scite/browser research inside a course-redesign run.\n---\n\n# Course Redesign Research\n\n## Lecturer Decision Dialogue Contract\n\nThe orchestrator is the sole lecturer-facing interface; specialist roles are\nevidence lenses and return questions through it. Ask one unresolved\nconsequential question at a time. Before using a native choice card, follow the\nlive host tool contract. Use a card only when it can present the complete,\nmutually exclusive option set and a custom-answer path without omission. Never\nprune, hide or combine valid choices merely to fit a card. If a native card is\nunavailable or unsupported, its capacity is unknown, or the complete set\nexceeds that capacity, ask the same single question in ordinary chat with every\nvalid numbered option plus `Other - type your answer`, then wait. Every valid\noption remains visible. For very\nlong decisions, use adaptive dependency-based clusters only when choices share\nevidence or constrain one another: keep every valid option visible, explain the\ngrouping and let the lecturer split, merge, reorder or rename it. For example,\noutcomes, assessment evidence, permitted AI use and learning activities belong\ntogether when mutually dependent; student-experience, accessibility and\nactive-learning perspectives may be clustered when participation design\njointly affects usability, inclusion, workload and engagement.\n\nPreserve a custom answer exactly, confirm its canonical interpretation, reflect\nthe consequence, and maintain a decision ledger in the chat and current state.\nShow an editable recap at each cluster or gate end. A skipped or blank response\nleaves a required question unresolved. The safest truthful, evidence-aligned,\nreversible option may be marked `Recommended`, but never preselected; factual\ndeclarations must say \"select only if true,\" and uncertainty fails closed. At\nmajor pedagogical gates, ask for the lecturer's criteria and preliminary view\nbefore recommending when practical. Exact authority gates and approval tokens\nremain separate and unchanged; a dialogue choice never substitutes for them.\n\nResearch only an approved focus and only within the current Gate-0A eligibility\nfingerprint and source-access policy. If either lineage value is missing,\nchanged or expired, stop before accessing course sources or sending a query.\n\n## Evidence protocol\n\nFor each consequential claim record:\n\n- atomic claim;\n- source and stable URL/DOI when available;\n- source class and authority;\n- publication/update date and currentness risk;\n- exact supporting location;\n- whether the source verifies quotation, date, authorship, interpretation, practice, or rights;\n- confidence, limitation, contradiction, and transfer boundary; and\n- audience/security classification.\n\nPrefer primary and authoritative sources: original texts/editions, official institutional guidance, legislation/policy, standards, and peer-reviewed research. Use reputable expert commentary for interpretation and implementation. Treat search snippets, vendor claims, blogs, and social media as leads unless the claim is appropriately limited.\n\n## Tools and egress\n\n- Public/open browser research may be used only if the run policy permits it.\n- Scite or another connector is optional; availability is not authorisation.\n- Never upload protected files, answer keys, assessment prompts, student data, or copyrighted extracts to an external tool unless exact egress is approved.\n- If a connector fails, record the exact failure and continue with approved alternatives; do not pretend it worked.\n\n## Text and fact verification\n\n- Name the controlling edition or official record.\n- Preserve source text; do not silently modernise spelling or punctuation.\n- Distinguish composed/written, first published/performed, and edition used.\n- Mark omissions and continued extracts explicitly.\n- Verify quotations line by line.\n- Never invent a citation, DOI, URL, timestamp, licence, rights holder, or publication fact.\n- Keep factual accuracy, citation completeness, and redistribution rights as separate judgements.\n\n## Synthesis\n\nConnect evidence to the exact supplied educational context, course level, discipline, outcomes, assessment construct, workload, accessibility, and local constraints. Treat school, vocational, professional and higher-education contexts as equally valid; label evidence from another context, discipline or learner group as indirect. Report disagreements and open controls instead of forcing consensus.\n\nFinish with a source ledger, claim table, decision implications, limitations, and exact items requiring lecturer judgement or specialist reconciliation.\n\nKeep the integrated dossier and handoff in the task/chat until Gate 2B. Write\nthem only after the lecturer approves their exact, dated targets under\n`03_Research/YYYY-MM-DD_<run-id>/`. That approval does not authorise course-\nmaterial production or any target under `04_Working_Copies/` or `05_Approved/`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}