{
  "skill": {
    "id": "feishu-doc-reporting",
    "name": "feishu-doc-reporting",
    "description": "Use when you need to turn notes, summaries, or research findings into a polished Feishu document artifact.",
    "path": "skills/feishu/feishu-doc-reporting/SKILL.md",
    "tags": [
      "feishu",
      "docs",
      "reporting",
      "workflow"
    ]
  },
  "document": {
    "path": "skills/feishu/feishu-doc-reporting/SKILL.md",
    "frontmatter": {
      "name": "feishu-doc-reporting",
      "description": "Use when you need to turn notes, summaries, or research findings into a polished Feishu document artifact.",
      "version": "0.1.0",
      "author": "Hermes Agent",
      "license": "private",
      "metadata": {
        "hermes": {
          "tags": [
            "feishu",
            "docs",
            "reporting",
            "workflow"
          ],
          "related_skills": [
            "internal-deep-research",
            "api-debugging"
          ]
        }
      }
    },
    "content": "---\nname: feishu-doc-reporting\ndescription: Use when you need to turn notes, summaries, or research findings into a polished Feishu document artifact.\nversion: 0.1.0\nauthor: Hermes Agent\nlicense: private\nmetadata:\n  hermes:\n    tags: [feishu, docs, reporting, workflow]\n    related_skills: [internal-deep-research, api-debugging]\n---\n\n# Feishu Doc Reporting\n\n## Overview\n\nUse this skill to package work into a Feishu document with a clean structure, readable headings, and a clear outcome. It is useful after research, project updates, meeting synthesis, or any task where the final result should live in a shareable doc rather than in chat.\n\n## When to Use\n\n- The user wants a report saved into Feishu\n- You have bullets, notes, or evidence that need document formatting\n- You need a standard report structure for repeated work\n- The deliverable should be easy to edit and circulate\n\n## Workflow\n\n1. Identify the report type and audience.\n2. Choose a concise title.\n3. Organize content into headings and short sections.\n4. Convert raw notes into readable prose and bullets.\n5. Add a summary at the top and clear action items at the bottom.\n6. Publish or update the Feishu document.\n\n## Suggested Structure\n\n- Title\n- Executive summary\n- Background\n- Findings\n- Actions / recommendations\n- Appendix or sources if needed\n\n## Common Pitfalls\n\n1. **Making the doc too long.** Prefer scannability.\n2. **Using chat formatting instead of doc structure.** Use headings and bullets intentionally.\n3. **Missing a clear takeaway.** The report should answer what matters and what happens next.\n4. **Forgetting the audience.** Technical and business reports should read differently.\n\n## Verification Checklist\n\n- [ ] The title is clear and specific\n- [ ] The document has headings\n- [ ] The summary is at the top\n- [ ] Action items or recommendations are explicit\n- [ ] The final artifact is accessible in Feishu\n"
  }
}