Research feishu report cocreate
Skill leohuang0423/deepresearch-report-feishu-skill/skills/openclaw/research-feishu-report-cocreate
Deep research report skill for Codex, Claude, and OpenClaw with Feishu-ready delivery
npx -y skills add leohuang0423/deepresearch-report-feishu-skill --skill research-feishu-report-cocreateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use for high-standard topic reports that need creator-first evidence, non-consensus synthesis, reader-first structure, structured dossiers, optional Feishu or HTML delivery, or bounded local-only synthesis.
SKILL.md
4.3 KB, as published. Nobody here has run it
Research Feishu Report Cocreation
Use this skill only for one task class:
- high-standard topic-sharing report
- multiple evidence objects
- explicit audience and decision value
- high-rework-cost convergence
- optional structured delivery
It is not for:
- generic writing
- lightweight research
- automatic product judgment or thesis generation
- vague brainstorming without a report contract
Read first:
contracts/mode_policy.yamlcontracts/gates.yamlreferences/workflow_v2.md
For heavy_topic_report, also read:
contracts/topic_report_brief.schema.yamlcontracts/expert_panels.yamlcontracts/rubric.yamlcontracts/state_machine.yamlreferences/research_cocreate_rules.mdreferences/creator_first_source_rules.mdreferences/non_consensus_insight_rules.mdreferences/reader_first_narrative_rules.mdreferences/case_packet_rules.mdreferences/report_visual_rules.mdreferences/local_only_synthesis_rules.md
Load on demand:
references/native_dossier_rules.mdreferences/feishu_publish_qa_rules.mdreferences/interactive_html_render_rules.mdreferences/main_doc_review_rules.mdreferences/eval_rules.md
Mandatory clarification loop
Before deep research, figure planning, or drafting:
- do one short framing pass
- sketch the initial plan
- scan the evidence boundary
Then ask the user 2-3 high-leverage clarification questions and wait for confirmation.
Prioritize:
- audience
- ideal-state result standard; make it as specific, evaluable, measurable, and quantifiable as possible
- decision goal or quality bar
- scope, source boundary, delivery shape, and must-include constraints
The clarification loop must align on what "excellent" looks like for this report using concrete acceptance criteria, evaluation dimensions, thresholds, examples, or numeric targets whenever possible.
Mode route
light: use the four-stage skeleton onlymid: expand one or two checkpointslocal_only_synthesis: keep the contract, compress intermediate states into final artifacts, and stay explicit about bounded evidenceheavy_topic_report: load contracts and follow the report-first path
Required heavy-mode panels:
ideal_state_panelevidence_panelacceptance_panel
Required heavy-mode sequence:
briefresearch_questionthesis_cardevidence_mapoutline_freezefigure_plandraftreview_panelacceptance_panel
Required local_only_synthesis sequence:
briefresearch_questionthesis_cardcompressed_evidence_mapoutline_freezedraftreview_panel
Required heavy-mode artifacts:
brief.yamlthesis_card.mdevidence_map.mdatomic_evidence.jsonlcase_packets/figure_manifest.yamlrender_manifest.yamlmain_report.mdappendix.mdrun_log.json
Required local_only_synthesis artifacts:
brief.yamlmain_report.mdappendix.mdrun_log.json
Modules
topic_to_reportcreator_source_miningnon_consensus_synthesisnarrative_architecturecase_packetingreport_visualslocal_only_synthesisnative_dossierfeishu_publish_qainteractive_html_report
Boundaries
- not a generic writer
- not a generic researcher
- not a product-judgment replacement
- not allowed to skip expert-panel checkpoints in heavy mode
- not allowed to continue into full research or drafting until
2-3 high-leverage clarification questionshave been asked after the initial first pass, unless the user already made them explicit - not allowed to treat "good quality" as sufficient alignment; the ideal-state result standard must be frozen as specifically and measurably as the task allows
- not allowed to skip the brief-to-outline path before drafting
- not allowed to fake external validation or full publish assets in
local_only_synthesis - not allowed to let market proof borrow certainty from mechanism proof
- not allowed to output a final report without appendix, creator-first evidence traceability, case packets, and explicit go / no-go thresholds