chore(apps): refine lark-apps skill description and surface

[raistlin042]

Summary

Documentation-only change to skills/lark-apps/SKILL.md (+8 / -1). No CLI code touched, no reference docs touched.

• Rewrite the skill description — switch from enumerating trigger phrases to one general principle: any HTML artifact intended to be independently accessible falls under this skill, and the deploy-vs-demo decision is left to the protocol inside the skill body (the existing "explicit deploy / demo only" branches in the in-body table). Also tighten the wording from "generate a shareable web page" to "generate a publicly accessible app and its URL", and add "configure app sharing scope" as a trigger scenario.
• Surface +access-scope-get — add it as item 6 in the prerequisites list and a new row in the bottom Shortcuts table, noting the response enum (All / Tenant / Range) maps to CLI flags (public / tenant / specific). The reference doc was already in place but unindexed from SKILL.md, so agents could not discover it for "view current scope" / "back up & copy scope config" scenarios.
• Add a "hard constraints before writing HTML" section — promote two CLI-side hard rejects to SKILL.md so agents stop hitting them only at publish time:
  • The entry file must be named index.html (app.html / demo.html etc. are rejected by +html-publish).
  • --path must not equal cwd (hard-rejected in source to prevent accidentally bundling .git / .env / node_modules into a publicly shareable URL).

Test plan

• Run a "write an HTML page that introduces X" prompt and verify the agent routes into this skill more reliably (the previous enumeration-style description was weak on cases that did not explicitly mention deploy / share).
• Ask the agent to "check the access scope of app X" and "back up app X's scope config to app Y" — verify it discovers +access-scope-get.
• Have the agent write app.html directly under cwd and request publish — verify it fixes the filename / path based on the new hard-constraints section before invoking publish, instead of waiting for a server-side reject.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the Lark Apps skill documentation by refining the skill description to focus on Miaoda deployment, adding prerequisite guidance for access scope retrieval, specifying hard constraints for HTML packaging (entry file name and directory path restrictions), and registering a new shortcut reference.

Changes

Lark Apps Skill Documentation

Layer / File(s)	Summary
Skill description and prerequisites skills/lark-apps/SKILL.md	The skill description is narrowed to focus on deploying HTML/directories to Miaoda. The apps +access-scope-get shortcut is added as a required pre-read step with notes on scope mapping and response details.
Packaging constraints and shortcuts skills/lark-apps/SKILL.md	A new "写 HTML 前的硬约束" section specifies that the entry file must be index.html and that --path cannot be the current working directory (.) to prevent accidental bundling of sensitive files. The +access-scope-get shortcut is added to the shortcuts table with a reference link.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

📚 A rabbit hops through docs with care,
Clarifying constraints in the air,
HTML rules and scope in sight,
Miaoda paths now burning bright! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title mentions 'refine lark-apps skill description and surface' which partially aligns with the main changes (description rewrite and surfacing +access-scope-get), though it lacks specificity about the new constraints section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The PR description comprehensively addresses all required sections with clear motivation, detailed change list, and explicit test plan validation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/apps-skill-optimize

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.75%. Comparing base (fbe4cc6) to head (8249774).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1040      +/-   ##
==========================================
- Coverage   67.76%   67.75%   -0.02%     
==========================================
  Files         590      590              
  Lines       55188    55188              
==========================================
- Hits        37398    37392       -6     
- Misses      14679    14684       +5     
- Partials     3111     3112       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🚀 PR Preview Install Guide

🧰 CLI update

npm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@8249774771d149b9472157073aca51dd557855bc

🧩 Skill update

npx skills add larksuite/cli#chore/apps-skill-optimize -y -g