CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

managed-lark-docs

Maintain and patch existing Lark/Feishu documents while preserving comments, highlights, citations, and newer remote edits. Use for iterative document updates, local-mirror sync, or durable project ownership; LoopX integration is optional.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered, safety-conscious instruction skill: the update workflow has explicit validation checkpoints and error-recovery loops, and guidance is concrete down to exact commands, layouts, and a manifest schema. The main costs are repetition of privacy rules across sections and inlining of detail (manifest contract, LoopX decisions) that could live in reference files.

Suggestions

State the privacy/raw-URL rule once in "Privacy And Git Decision" and reference it from the other sections instead of repeating it in Non-Negotiable Defaults, Local Layout, and Output Standard.

Show one minimal concrete patch round inline (fetch affected XML → single block replacement → read back and confirm anchors), so the core write operation does not depend entirely on delegating to `lark-doc`.

Move the manifest JSON contract and the LoopX registration workflow details into a reference file to shorten the SKILL.md body closer to an overview.

DimensionReasoningScore

Conciseness

The ~270-line body is dense and operational with no explanations of concepts Claude already knows, but the privacy/raw-URL rule is restated in four places (Non-Negotiable Defaults, Local Layout, Privacy And Git Decision, Output Standard) and the LoopX link appears three times. This is minor trimmable repetition, matching the efficient-with-minor-overexplanation anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete throughout: exact directory layout, a full manifest JSON contract, `git check-ignore -v`, `lark-cli skills read <path>`, an ordered patch-preference list, and explicit classification labels (preserve/merge/ask_user/explicit_replace). It stops short of fully copy-paste-ready because the core Lark write commands are delegated to the `lark-doc` skill rather than shown, matching the mostly-executable anchor at 4.

4 / 5

Workflow Clarity

The six-step Managed Update Workflow has explicit validation checkpoints (freshness/revision comparison, protected-anchor mapping, a 6-item verify-and-write-back checklist) and genuine feedback loops: revision-conflict retry ("fetch and merge the new remote state before retrying"), read-back after each patch round, and partial-success handling ("never replay a partially applied batch blindly"). This matches the clear-sequence-with-explicit-validation-and-error-recovery anchor.

5 / 5

Progressive Disclosure

Both bundle references exist, are one level deep, and are clearly signaled with read conditions ("Read references/comment-preserving-sync.md before changing content with comments, highlights…"; the LoopX reference is linked at each relevant decision point). Scored 4 rather than 5 because the long body inlines material that could be externalized, such as the full manifest JSON contract and the LoopX decision table, keeping the split from being maximally clean.

4 / 5

Total

17

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with a concrete capability statement and an explicit "Use for" trigger clause covering both platform synonyms. Its weaknesses are minor: a couple of missing natural trigger phrases and one abstract use case ("durable project ownership") in the when-clause.

Suggestions

Replace or supplement the abstract "durable project ownership" trigger with a phrase a user would actually say, e.g. "Use when the user asks to update, sync, or take long-term ownership of a Lark/Feishu doc without losing comments or tracked changes".

Add natural trigger synonyms such as 飞书 (the Chinese name for Feishu), "doc comments", and "review feedback" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Maintain and patch existing Lark/Feishu documents while preserving comments, highlights, citations, and newer remote edits" lists several concrete actions (patch, preserve comments/highlights/citations, respect newer remote edits) in a named domain. Not 5 because it omits the sync/verify/manifest operations the body actually performs; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Both what ("Maintain and patch existing Lark/Feishu documents while preserving…") and when ("Use for iterative document updates, local-mirror sync, or durable project ownership") are explicit. Scored 4 rather than 5 because "durable project ownership" is abstract jargon a user would not naturally say, leaving the when-clause only partly concrete.

4 / 5

Trigger Term Quality

"Lark/Feishu" covers both platform synonyms, and "document updates", "local-mirror sync", "comments", "citations" are natural terms. A few natural phrases are missing (e.g. the Chinese platform name 飞书, plain "doc edit", "review comments"), so it falls short of the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The Lark/Feishu platform niche plus preservation-focused differentiators (comments, highlights, newer remote edits) make it mostly distinct. Minor overlap risk remains with sibling lark-doc/lark-drive skills that also edit Lark documents, so it does not reach the clear-niche anchor at 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huangruiteng/CS-Notes

Path

.codex/skills/managed-lark-docs/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.