القائمة
Audit source quality, scoring performance, duplicate patterns, source failures, stale config, and tuning opportunities.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/grandamenium/cortextos --skill research-quality-reviewيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
You need to write or update memory. This happens at session start, heartbeat, session end, or when you learn something worth keeping. Memory is how you maintain continuity across restarts and context compactions — without it, every session starts blind.
You need to write or update memory. This happens at session start, heartbeat, session end, or when you learn something worth keeping. Memory is how you maintain continuity across restarts and context compactions — without it, every session starts blind.
Migrate ANY cortextOS agent from the claude-code runtime to the live codex-app-server runtime. Use this whenever a user wants to convert, port, move, or switch a Claude-cortextOS agent to Codex / gpt-5-codex / gpt-5.5, "make agent X run on codex", "turn this claude agent into a codex agent", or asks how a Claude agent's CLAUDE.md / .claude/skills / .mcp.json / hooks map onto the codex-app-server adapter. Takes a source agent name and produces a SEPARATE codex-shaped agent (non-destructive, dry-run by default). Trigger even if they only say "migrate <agent> to codex" without naming the artifacts. Do NOT use for creating a brand-new codex agent from scratch (use `cortextos add-agent`) or for hermes/orchestrator/analyst runtimes.
| name | research-quality-review |
| description | Audit source quality, scoring performance, duplicate patterns, source failures, stale config, and tuning opportunities. |
Run weekly, after a few research cycles, or whenever the briefs feel noisy.
research/output/research/topic-briefings/research/sources.jsonresearch/scoring-rubric.jsonresearch/db/signals.db if availableWrite:
research/output/YYYY-MM-DD/research-quality-review.md
Use this format:
# Research Quality Review -- YYYY-MM-DD
## Summary
[What is working / not working.]
## Source Changes Recommended
- Keep:
- Add:
- Remove:
- Watch:
## Scoring Changes Recommended
- [Specific rubric edit and why]
## Workflow Changes Recommended
- [Cron, delivery, topic briefing, output format changes]
## Human Decisions Needed
- [Decision and tradeoff]
Do not edit source/scoring config automatically unless the user asks. Propose changes first.