feishu-logger_skill

Overview

This skill collects and records document creation results into persistent logs in both Markdown and JSON formats. It centralizes outputs from parsing, block addition, permission changes, and verification steps so you can audit what happened during a document creation workflow. The skill is designed to be invoked from the command line or as a sub-skill by other workflows.

How this skill works

It loads JSON result files from a workflow directory (blocks.json, doc_info.json, add_result.json, permission_result.json, verify_result.json). The skill extracts key fields such as document ID, URL, permission and verification statuses, and counts of blocks/tables created. It appends a human-readable entry to CREATED_DOCS.md and a machine-friendly record to created_docs.json, then prints a concise summary to the console.

When to use it

• After running a document creation workflow to capture final outcomes
• When you need an audit trail for created documents and permission changes
• Before or after handoff to other systems that require document metadata
• As part of CI/CD or automated pipelines that generate documents programmatically

Best practices

• Ensure all expected result files are present in the workflow directory before invoking the logger
• Standardize keys in intermediate result files so the logger can reliably extract values
• Run the logger as the last step in your workflow to capture final states
• Store CREATED_DOCS.md and created_docs.json in a central output directory for easy review and integration

Example use cases

• Append a detailed Markdown entry for each created document to share with stakeholders
• Produce a JSON index of created documents for downstream automation or analytics
• Record permission operations and verification outcomes for compliance audits
• Integrate into nightly pipelines to keep a historical log of document generation activity