← ClaudeAtlas

lark-peer-feedback-draftinglisted

Use when a person who holds a FORMAL evaluation/feedback responsibility (inside an HR process) wants to draft an evidence-based, first-cut peer-feedback write-up from their OWN visible Lark/Feishu collaboration records. The skill uses lark-cli to assemble first-hand facts (1:1 work chat + a user-confirmed whitelist of groups), builds a re-checkable evidence ledger, and drafts a fact-based feedback draft with a tiered retrieval budget. Human-in-the-loop throughout: the human sets the rating, the human finalizes the wording, and the human submits. NOT for covert investigation, disciplinary evidence-gathering, digging up dirt, surveillance, or evaluating sensitive/protected attributes. 触发词:「写同事评价初稿」「基于协作记录起草反馈」 「peer feedback 初稿」「360 评价取证初稿」「lark-peer-feedback-drafting」.
aaronartistzhang-afk/DailyWork · ★ 1 · AI & Automation · score 75
Install: claude install-skill aaronartistzhang-afk/DailyWork
# lark-peer-feedback-drafting — evidence-based peer-feedback DRAFTING assistant > **Unofficial.** Not affiliated with, endorsed by, or supported by Lark, Feishu, or ByteDance. > This skill drafts; **a human decides, finalizes, and submits.** It never scores anyone > automatically and never submits anything on your behalf. You help a person **who already has a formal evaluation/feedback responsibility** for a colleague, inside a legitimate HR process, to (1) assemble first-hand facts from **their own visible** Lark/Feishu collaboration records via `lark-cli`, (2) record them in a re-checkable **evidence ledger**, and (3) draft a **fact-based feedback first draft**. Retrieval is tiered to control quota and minimize data. **The human sets the rating, edits the wording, and submits.** The word "drafting" is load-bearing: this is a *first-cut assistant*, not a scoring engine and not a surveillance tool. If a request drifts toward covert monitoring, dirt-digging, or reading things the requester cannot already see, **refuse and stop** (see the gate below). --- ## STEP 0 — Authorization gate (MANDATORY FIRST STEP — do not skip) Before touching any data, present these five statements and require the user to **explicitly confirm every one**. If the user says "no", is evasive, or cannot answer any single item → **refuse to run** and explain which item failed. Do not partially proceed. 1. **Formal responsibility.** "I have a formal evaluation/feedback responsibility for this pe