pmai-sync-from-lark

Syncs Feishu Docx document bodies back into local Markdown files without product judgment.

4|Updated May 26, 2026
One-click install
npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-sync-from-lark-yyg501
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmai-sync-from-lark
Source: https://github.com/YYG501/PM-AI-Harness/tree/main/skills/sync-from-lark
Command: npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-sync-from-lark-yyg501

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a PM has finalized content in a Feishu (Lark) Docx document and explicitly wants the local Markdown spec to match it, manually copying content risks losing frontmatter, mixing in stale local text, or overwriting uncommitted work. This Skill performs a guarded, mechanical one-way sync from Feishu to local Markdown. ## Core Features & Use Cases - Mechanical body replacement: Pulls the Feishu Docx Markdown body and atomically replaces only the local body, preserving the original frontmatter including unknown fields and comments. - Diff-only preview: Compares local and Feishu content section by section and reports additions, deletions, and wording differences without writing anything. - Safety guardrails: Refuses to run when the target file has uncommitted changes, when the module has an active build, or when the PM's intent still requires product judgment (redirecting to pmai-lark-review). - Use Case: A PM says "the Feishu doc is final, sync it back, no judgment needed." The Skill verifies the working tree is clean, fetches the Feishu revision, replaces only the Markdown body, refreshes the alignment baseline, and reports exactly what changed. ## Quick Start Tell the assistant to sync the finalized Feishu document back into the local Markdown spec at docs/specs/checkout.md because Feishu is the final version and no product judgment is needed.

Frequently Asked Questions about pmai-sync-from-lark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync a Feishu Docx document back to local Markdown?

Provide the local Markdown path or the Feishu Docx URL and explicitly confirm the Feishu version is final. The Skill fetches the Feishu Markdown via lark-cli, replaces only the local body, and preserves the original frontmatter verbatim.

How can I preview differences between Feishu and local docs before syncing?

Ask for a diff-only preview. The Skill compares section by section, reporting Feishu additions, deletions, and wording differences in a table without modifying either side, so you can decide whether to sync or escalate to review.

When should I use pmai-lark-review instead of sync-from-lark?

Use pmai-lark-review whenever Feishu edits or comments might affect product decisions, specs, prototypes, or implementation. sync-from-lark only runs when the PM explicitly waives judgment and declares Feishu as the final source.

Why does the Feishu sync stop with uncommitted local changes?

The Skill halts when the target Markdown has uncommitted body changes because syncing would overwrite that work. It reports the exact files at risk and waits for the PM to commit or explicitly confirm before writing.

Does syncing from Feishu update decisions, prototypes, or code?

No. The Skill only modifies the single target Markdown body. It never touches decisions.md, proposals, prototypes, or implementation files, and it refuses to run during an active build on the target module.