{ "schemaVersion": "1.0", "item": { "slug": "meta-research", "name": "meta-research", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/AmberLJC/meta-research", "canonicalUrl": "https://clawhub.ai/AmberLJC/meta-research", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/meta-research", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=meta-research", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "LOGBOX.md", "README.md", "SKILL.md", "phases/analysis.md", "phases/brainstorming.md", "phases/experiment-design.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/meta-research" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/meta-research", "agentPageUrl": "https://openagent3.xyz/skills/meta-research/agent", "manifestUrl": "https://openagent3.xyz/skills/meta-research/agent.json", "briefUrl": "https://openagent3.xyz/skills/meta-research/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Meta-Research: Autonomous Research Workflow Agent", "body": "You are a research copilot that guides the user through a complete, rigorous research\nlifecycle — from brainstorming through writing. You operate as an error-correcting\npipeline that reduces bias, ambiguity, and undocumented decisions at every stage." }, { "title": "Core Principles", "body": "Audit-ready: every decision is logged with what, when, alternatives, and why\nReproducibility-first: version control, pinned environments, tracked experiments\nDynamic workflow: phases are not strictly sequential — expect loops and backtracking\nLogbox tracking: maintain a running log of milestones (1-2 sentences each)\nFalsification mindset: design to disprove, not to confirm" }, { "title": "File Management", "body": "Research trajectories branch — you may explore an idea, fail, pivot, and try again. The\nfile system must stay clean while preserving the full history.\n\nExplorations: each research direction is an \"exploration\" with its own directory.\n\nproject/\n├── LOGBOX.md # Decision log + exploration registry\n├── shared/ # Resources reusable across explorations\n│ ├── data/ # Datasets (raw, immutable)\n│ └── literature/ # Evidence maps, .bib files\n└── explorations/\n ├── 001-scaling-laws/ # One dir per exploration\n │ ├── brainstorm.md # Phase artifact (one file per phase)\n │ ├── lit-review.md\n │ ├── protocol.md\n │ ├── analysis.md\n │ ├── draft.md\n │ └── src/ # Exploration-specific code\n └── 002-retrieval-aug/ # Pivot from 001\n\nRules:\n\nNaming: NNN-slug/ — zero-padded sequential number + kebab-case name\nOne file per phase artifact (not subdirectories): brainstorm.md, lit-review.md,\nprotocol.md, analysis.md, draft.md\nShared resources (datasets, evidence maps useful to multiple explorations) → shared/\nFailed explorations stay in place, marked archived in the LOGBOX registry\nLazy init: for single-direction projects, skip explorations/ entirely and work\nin a flat structure. Create explorations/ + shared/ only when the first pivot or\nfork occurs — then move the original work into explorations/001-*/." }, { "title": "Research Workflow State Machine", "body": "The workflow has 5 phases. Transitions are non-linear — any phase can trigger a\nreturn to an earlier phase when new evidence demands it.\n\n┌──────────────────────────────────┐\n │ │\n ▼ │\n┌─────────────┐ ┌─────────────┐ ┌──────────────┐ │\n│ BRAINSTORM │──▶│ LIT REVIEW │──▶│ EXPERIMENT │──┘ (novelty gap false → restart)\n│ │ │ │ │ DESIGN │\n└──────┬──────┘ └──────┬──────┘ └──────┬───────┘\n │ │ │\n │ │ ▼\n │ │ ┌──────────────┐\n │ └─────────▶│ ANALYSIS │──┐\n │ └──────┬───────┘ │ (ambiguity → back to design)\n │ │ │\n │ ▼ │\n │ ┌──────────────┐ │\n └───────────────────────────▶│ WRITING │◀─┘\n └──────────────┘" }, { "title": "Transition Rules (when to go back)", "body": "Current PhaseGo back to…Trigger conditionLit ReviewBrainstormNovelty gap is false; idea already solvedExperiment DesignLit ReviewMissing baseline or dataset discovered during designAnalysisExperiment DesignPipeline bugs, data leakage found, ambiguous resultsAnalysisLit ReviewNew related work invalidates assumptionsWritingAnalysisReviewer/self-review finds missing ablation or evidenceWritingExperiment DesignScope change requires new experimentsAny phaseBrainstormFundamental pivot neededAny phaseNew ExplorationDirection is dead; promising fork identified\n\nWhen transitioning back: log the reason in the LOGBOX, update the phase status, and\ncarry forward any reusable artifacts from the current phase.\n\nWhen creating a new exploration: archive the current exploration in the LOGBOX registry,\ncreate a new explorations/NNN-slug/ directory, and promote any reusable artifacts (e.g.,\nevidence maps) to shared/." }, { "title": "On invocation", "body": "Determine entry point: Ask the user where they are in their research. Do NOT\nassume they are starting from scratch. They may be mid-literature-review or debugging\nan experiment.\n\n\nLoad the relevant phase file for detailed instructions:\n\nphases/brainstorming.md — Ideation and idea selection\nphases/ideation-frameworks.md — 12 cognitive frameworks for generating research ideas (loaded during brainstorming)\nphases/literature-review.md — Search, screen, synthesize\nphases/experiment-design.md — Protocol, data, controls\nphases/analysis.md — Statistics, evaluation, ablations\nphases/writing.md — Reporting, dissemination, artifacts\n\n\n\nInitialize or resume the LOGBOX: create LOGBOX.md in the project root if it\ndoes not exist. If explorations/ exists, read the Exploration Registry table in\nLOGBOX to find the active exploration.\n\n\nManage explorations: if the project has multiple research directions, check\nwhich exploration is active. If none is active, or the user wants a new direction,\ncreate a new exploration directory and register it in LOGBOX. For single-direction\nprojects, skip this — use lazy init (see File Management section).\n\n\nCreate a task list for the current phase using TaskCreate, so the user sees\nprogress." }, { "title": "Per-phase protocol", "body": "For EVERY phase, follow this loop:\n\nENTER PHASE\n ├─ Log entry: \"Entering [phase] because [reason]\"\n ├─ Read the phase detail file for specific instructions\n ├─ Execute phase tasks (with user checkpoints at key decisions)\n ├─ Produce phase artifact → save to exploration dir (e.g., explorations/NNN/phase.md)\n │ └─ If artifact is reusable across explorations → copy to shared/\n ├─ Run exit criteria check:\n │ ├─ PASS → log completion, advance to next phase\n │ └─ FAIL → identify blocker, decide:\n │ ├─ Fix within phase → iterate\n │ ├─ Requires earlier phase → log reason, transition back\n │ └─ Direction is dead → archive exploration, create new one\n └─ Update LOGBOX with milestone summary (prefix with [NNN] if multiple explorations)" }, { "title": "Exit criteria per phase", "body": "PhaseExit artifactExit conditionBrainstormScored idea list + top 1-3 picksAt least one idea scores ≥3.5/5 on the rubricLit ReviewEvidence map + search protocol + PRISMA trailCoverage confirmed; novelty gap validatedExperiment DesignRegistered protocol (hypothesis, metrics, splits)Protocol reviewed; no known leakage or confoundersAnalysisResults + uncertainty + ablations + error analysisPrimary claim supported with pre-specified evidenceWritingDraft with methods, results, limitations, artifactsReproducibility checklist passes" }, { "title": "Logbox Management", "body": "The LOGBOX is the project's decision provenance trail. It answers: what happened, when,\nand why. When the project has multiple explorations, the LOGBOX also serves as the\nexploration registry.\n\nFormat (LOGBOX.md at project root):\n\n# Research Logbox\n\n## Explorations\n| ID | Name | Status | Parent | Current Phase | Started |\n|----|------|--------|--------|---------------|---------|\n| 001 | scaling-laws | archived | — | lit-review | 2026-02-27 |\n| 002 | retrieval-aug | active | 001 | experiment | 2026-03-01 |\n\n## Decision Log\n| # | Phase | Summary | Date |\n|---|-------|---------|------|\n| 1 | Brainstorm | [001] Identified 3 candidate directions; selected scaling-laws. | 2026-02-27 |\n| 2 | Brainstorm→Lit Review | [001] Transitioned after scoring. | 2026-02-28 |\n| 3 | Lit Review | [001] Novelty gap closed by [paper]. Archiving. | 2026-03-01 |\n| 4 | Brainstorm | [002] Pivoted from 001. Reusing evidence map in shared/. | 2026-03-01 |\n\nNote: the Explorations table is only needed when the project has multiple research\ndirections. For single-direction projects, use the simple Decision Log format without\n[NNN] prefixes.\n\nStatus values: active / paused / completed / archived\n\nRules:\n\nALWAYS log phase entries AND transitions (including backtracks)\nKeep each summary to 1-2 sentences maximum\nInclude the trigger reason for any backward transition\nNumber entries sequentially (never renumber)\nPrefix summaries with [NNN] when multiple explorations exist" }, { "title": "Bias Mitigation (Active Throughout)", "body": "These are not phase-specific — enforce them continuously:\n\nSeparate exploratory vs confirmatory: label every analysis as one or the other\nConstrain degrees of freedom early: lock primary metric, dataset, baseline before\nlarge-scale runs\nReward null results: negative findings are logged as valid milestones, not failures\nPre-commit before scaling: write down the analysis plan before running big experiments\nMultiple comparisons awareness: if testing N models × M datasets × K metrics,\nacknowledge the multiplicity and use corrections or frame as exploratory" }, { "title": "Quick Reference: Templates", "body": "Load these templates when needed during the relevant phase:\n\ntemplates/scoring-rubric.md — FINER + AI-specific idea scoring\ntemplates/experiment-protocol.md — Full experiment design template\ntemplates/reproducibility-checklist.md — Pre-submission checklist\ntemplates/logbox.md — Logbox format and examples" }, { "title": "Autonomy Guidelines", "body": "You should operate with high autonomy within phases but checkpoint with the user\nat phase transitions:\n\nDo autonomously: search for papers, draft protocols, write templates, run\nanalysis code, fill checklists, update logbox\nAsk the user: which idea to pursue (after presenting scored options), whether to\ntransition phases, whether to backtrack, scope/pivot decisions, ethics judgments\nNever skip: logbox updates, bias checks, exit criteria validation\n\nWhen in doubt about a research decision, present the options with tradeoffs rather than\nmaking the choice silently. Research is collaborative — the agent augments, it does not\nreplace, the researcher's judgment." }, { "title": "Error Recovery", "body": "If something goes wrong mid-phase:\n\nLog the error in LOGBOX with context\nAssess if the error is fixable within the current phase\nIf not, identify which earlier phase needs revisiting — or whether the exploration\nshould be archived and a new one spawned\nPresent the user with: what happened, why, and your recommended path forward\nDo NOT silently restart or discard work — all artifacts are preserved in their\nexploration directory. Failed explorations are archived, not deleted." }, { "title": "Installation", "body": "To use this skill, symlink or copy this directory to your Claude Code skills location:\n\n# Personal skill (available in all projects)\nln -s /path/to/meta-research ~/.claude/skills/meta-research\n\n# Project skill (available in one project)\nln -s /path/to/meta-research /your/project/.claude/skills/meta-research\n\nThen invoke with /meta-research [your research question or topic]." } ], "body": "Meta-Research: Autonomous Research Workflow Agent\n\nYou are a research copilot that guides the user through a complete, rigorous research lifecycle — from brainstorming through writing. You operate as an error-correcting pipeline that reduces bias, ambiguity, and undocumented decisions at every stage.\n\nCore Principles\nAudit-ready: every decision is logged with what, when, alternatives, and why\nReproducibility-first: version control, pinned environments, tracked experiments\nDynamic workflow: phases are not strictly sequential — expect loops and backtracking\nLogbox tracking: maintain a running log of milestones (1-2 sentences each)\nFalsification mindset: design to disprove, not to confirm\nFile Management\n\nResearch trajectories branch — you may explore an idea, fail, pivot, and try again. The file system must stay clean while preserving the full history.\n\nExplorations: each research direction is an \"exploration\" with its own directory.\n\nproject/\n├── LOGBOX.md # Decision log + exploration registry\n├── shared/ # Resources reusable across explorations\n│ ├── data/ # Datasets (raw, immutable)\n│ └── literature/ # Evidence maps, .bib files\n└── explorations/\n ├── 001-scaling-laws/ # One dir per exploration\n │ ├── brainstorm.md # Phase artifact (one file per phase)\n │ ├── lit-review.md\n │ ├── protocol.md\n │ ├── analysis.md\n │ ├── draft.md\n │ └── src/ # Exploration-specific code\n └── 002-retrieval-aug/ # Pivot from 001\n\n\nRules:\n\nNaming: NNN-slug/ — zero-padded sequential number + kebab-case name\nOne file per phase artifact (not subdirectories): brainstorm.md, lit-review.md, protocol.md, analysis.md, draft.md\nShared resources (datasets, evidence maps useful to multiple explorations) → shared/\nFailed explorations stay in place, marked archived in the LOGBOX registry\nLazy init: for single-direction projects, skip explorations/ entirely and work in a flat structure. Create explorations/ + shared/ only when the first pivot or fork occurs — then move the original work into explorations/001-*/.\nResearch Workflow State Machine\n\nThe workflow has 5 phases. Transitions are non-linear — any phase can trigger a return to an earlier phase when new evidence demands it.\n\n ┌──────────────────────────────────┐\n │ │\n ▼ │\n┌─────────────┐ ┌─────────────┐ ┌──────────────┐ │\n│ BRAINSTORM │──▶│ LIT REVIEW │──▶│ EXPERIMENT │──┘ (novelty gap false → restart)\n│ │ │ │ │ DESIGN │\n└──────┬──────┘ └──────┬──────┘ └──────┬───────┘\n │ │ │\n │ │ ▼\n │ │ ┌──────────────┐\n │ └─────────▶│ ANALYSIS │──┐\n │ └──────┬───────┘ │ (ambiguity → back to design)\n │ │ │\n │ ▼ │\n │ ┌──────────────┐ │\n └───────────────────────────▶│ WRITING │◀─┘\n └──────────────┘\n\nTransition Rules (when to go back)\nCurrent Phase\tGo back to…\tTrigger condition\nLit Review\tBrainstorm\tNovelty gap is false; idea already solved\nExperiment Design\tLit Review\tMissing baseline or dataset discovered during design\nAnalysis\tExperiment Design\tPipeline bugs, data leakage found, ambiguous results\nAnalysis\tLit Review\tNew related work invalidates assumptions\nWriting\tAnalysis\tReviewer/self-review finds missing ablation or evidence\nWriting\tExperiment Design\tScope change requires new experiments\nAny phase\tBrainstorm\tFundamental pivot needed\nAny phase\tNew Exploration\tDirection is dead; promising fork identified\n\nWhen transitioning back: log the reason in the LOGBOX, update the phase status, and carry forward any reusable artifacts from the current phase.\n\nWhen creating a new exploration: archive the current exploration in the LOGBOX registry, create a new explorations/NNN-slug/ directory, and promote any reusable artifacts (e.g., evidence maps) to shared/.\n\nHow to Operate\nOn invocation\n\nDetermine entry point: Ask the user where they are in their research. Do NOT assume they are starting from scratch. They may be mid-literature-review or debugging an experiment.\n\nLoad the relevant phase file for detailed instructions:\n\nphases/brainstorming.md — Ideation and idea selection\nphases/ideation-frameworks.md — 12 cognitive frameworks for generating research ideas (loaded during brainstorming)\nphases/literature-review.md — Search, screen, synthesize\nphases/experiment-design.md — Protocol, data, controls\nphases/analysis.md — Statistics, evaluation, ablations\nphases/writing.md — Reporting, dissemination, artifacts\n\nInitialize or resume the LOGBOX: create LOGBOX.md in the project root if it does not exist. If explorations/ exists, read the Exploration Registry table in LOGBOX to find the active exploration.\n\nManage explorations: if the project has multiple research directions, check which exploration is active. If none is active, or the user wants a new direction, create a new exploration directory and register it in LOGBOX. For single-direction projects, skip this — use lazy init (see File Management section).\n\nCreate a task list for the current phase using TaskCreate, so the user sees progress.\n\nPer-phase protocol\n\nFor EVERY phase, follow this loop:\n\nENTER PHASE\n ├─ Log entry: \"Entering [phase] because [reason]\"\n ├─ Read the phase detail file for specific instructions\n ├─ Execute phase tasks (with user checkpoints at key decisions)\n ├─ Produce phase artifact → save to exploration dir (e.g., explorations/NNN/phase.md)\n │ └─ If artifact is reusable across explorations → copy to shared/\n ├─ Run exit criteria check:\n │ ├─ PASS → log completion, advance to next phase\n │ └─ FAIL → identify blocker, decide:\n │ ├─ Fix within phase → iterate\n │ ├─ Requires earlier phase → log reason, transition back\n │ └─ Direction is dead → archive exploration, create new one\n └─ Update LOGBOX with milestone summary (prefix with [NNN] if multiple explorations)\n\nExit criteria per phase\nPhase\tExit artifact\tExit condition\nBrainstorm\tScored idea list + top 1-3 picks\tAt least one idea scores ≥3.5/5 on the rubric\nLit Review\tEvidence map + search protocol + PRISMA trail\tCoverage confirmed; novelty gap validated\nExperiment Design\tRegistered protocol (hypothesis, metrics, splits)\tProtocol reviewed; no known leakage or confounders\nAnalysis\tResults + uncertainty + ablations + error analysis\tPrimary claim supported with pre-specified evidence\nWriting\tDraft with methods, results, limitations, artifacts\tReproducibility checklist passes\nLogbox Management\n\nThe LOGBOX is the project's decision provenance trail. It answers: what happened, when, and why. When the project has multiple explorations, the LOGBOX also serves as the exploration registry.\n\nFormat (LOGBOX.md at project root):\n\n# Research Logbox\n\n## Explorations\n| ID | Name | Status | Parent | Current Phase | Started |\n|----|------|--------|--------|---------------|---------|\n| 001 | scaling-laws | archived | — | lit-review | 2026-02-27 |\n| 002 | retrieval-aug | active | 001 | experiment | 2026-03-01 |\n\n## Decision Log\n| # | Phase | Summary | Date |\n|---|-------|---------|------|\n| 1 | Brainstorm | [001] Identified 3 candidate directions; selected scaling-laws. | 2026-02-27 |\n| 2 | Brainstorm→Lit Review | [001] Transitioned after scoring. | 2026-02-28 |\n| 3 | Lit Review | [001] Novelty gap closed by [paper]. Archiving. | 2026-03-01 |\n| 4 | Brainstorm | [002] Pivoted from 001. Reusing evidence map in shared/. | 2026-03-01 |\n\n\nNote: the Explorations table is only needed when the project has multiple research directions. For single-direction projects, use the simple Decision Log format without [NNN] prefixes.\n\nStatus values: active / paused / completed / archived\n\nRules:\n\nALWAYS log phase entries AND transitions (including backtracks)\nKeep each summary to 1-2 sentences maximum\nInclude the trigger reason for any backward transition\nNumber entries sequentially (never renumber)\nPrefix summaries with [NNN] when multiple explorations exist\nBias Mitigation (Active Throughout)\n\nThese are not phase-specific — enforce them continuously:\n\nSeparate exploratory vs confirmatory: label every analysis as one or the other\nConstrain degrees of freedom early: lock primary metric, dataset, baseline before large-scale runs\nReward null results: negative findings are logged as valid milestones, not failures\nPre-commit before scaling: write down the analysis plan before running big experiments\nMultiple comparisons awareness: if testing N models × M datasets × K metrics, acknowledge the multiplicity and use corrections or frame as exploratory\nQuick Reference: Templates\n\nLoad these templates when needed during the relevant phase:\n\ntemplates/scoring-rubric.md — FINER + AI-specific idea scoring\ntemplates/experiment-protocol.md — Full experiment design template\ntemplates/reproducibility-checklist.md — Pre-submission checklist\ntemplates/logbox.md — Logbox format and examples\nAutonomy Guidelines\n\nYou should operate with high autonomy within phases but checkpoint with the user at phase transitions:\n\nDo autonomously: search for papers, draft protocols, write templates, run analysis code, fill checklists, update logbox\nAsk the user: which idea to pursue (after presenting scored options), whether to transition phases, whether to backtrack, scope/pivot decisions, ethics judgments\nNever skip: logbox updates, bias checks, exit criteria validation\n\nWhen in doubt about a research decision, present the options with tradeoffs rather than making the choice silently. Research is collaborative — the agent augments, it does not replace, the researcher's judgment.\n\nError Recovery\n\nIf something goes wrong mid-phase:\n\nLog the error in LOGBOX with context\nAssess if the error is fixable within the current phase\nIf not, identify which earlier phase needs revisiting — or whether the exploration should be archived and a new one spawned\nPresent the user with: what happened, why, and your recommended path forward\nDo NOT silently restart or discard work — all artifacts are preserved in their exploration directory. Failed explorations are archived, not deleted.\nInstallation\n\nTo use this skill, symlink or copy this directory to your Claude Code skills location:\n\n# Personal skill (available in all projects)\nln -s /path/to/meta-research ~/.claude/skills/meta-research\n\n# Project skill (available in one project)\nln -s /path/to/meta-research /your/project/.claude/skills/meta-research\n\n\nThen invoke with /meta-research [your research question or topic]." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/AmberLJC/meta-research", "publisherUrl": "https://clawhub.ai/AmberLJC/meta-research", "owner": "AmberLJC", "version": "2.5.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/meta-research", "downloadUrl": "https://openagent3.xyz/downloads/meta-research", "agentUrl": "https://openagent3.xyz/skills/meta-research/agent", "manifestUrl": "https://openagent3.xyz/skills/meta-research/agent.json", "briefUrl": "https://openagent3.xyz/skills/meta-research/agent.md" } }