Skip to content

docs: fix eight broken links in shipped skill references #2480

Description

@dajiaohuang

Baseline

main at 35bd5ecfcd84c8e457323a1bcf9453ba600c0270.

Problem

Eight relative links in shipped skill documentation resolve to files that do not exist:

  1. Six files under skills/lark-mail/references/ link to references/lark-mail-html.md, which resolves to the nonexistent references/references/lark-mail-html.md:
    • lark-mail-draft-create.md
    • lark-mail-draft-edit.md
    • lark-mail-forward.md
    • lark-mail-reply-all.md
    • lark-mail-reply.md
    • lark-mail-send.md
  2. skills/lark-apps/references/lark-apps-local-dev.md links to ../creative-design/SKILL.md; the actual entry is ../creative-design/creative-design.md.
  3. skills/lark-mail/references/lark-mail-watch.md links to ../../lark-event/references/lark-event-subscribe.md, which is absent; the generic event-consumption guidance is in ../../lark-event/SKILL.md.

Expected behavior

Every relative link in shipped skill guidance should resolve within the installed skill tree so an agent can follow required and referenced instructions.

Impact

The six mail links are marked as required reading before composing or editing complex HTML, while the other two links break the documented app-design and event-consumption workflows.

Suggested fix

  • Change the six mail-reference targets to lark-mail-html.md.
  • Point the local app workflow to ../creative-design/creative-design.md.
  • Point mail watch to ../../lark-event/SKILL.md.

Duplicate check

I searched open and closed issues, all PR states, and commits for the exact target paths. Open mail PRs that touch these files still contain the same links at their current heads, including #787, #834, #851, #899, #1134, #1282, #1534, #1542, #1650, and #1687; none is a competing link fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdomain/coreCLI framework and core libraries

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions