一键在 Manus 中运行任何 Skill

link-text-review

星标146

分支304

更新时间2026年6月29日 15:28

Review and improve accessible Markdown link text in Arm Learning Paths and install guides. Use when asked to find vague links, fix link text such as here or click here, verify internal links, improve screen-reader clarity, or make links descriptive and task-focused.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

ArmDeveloperEcosystem

ArmDeveloperEcosystem/arm-learning-paths

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Link text review

Use this skill to review or improve Markdown link text so links are descriptive, accessible, and useful out of context.

This skill focuses on anchor text and link clarity. For tables, notices, tab panes, and other structural Markdown components, use .github/skills/markdown-component-edit/SKILL.md.

Prerequisites

Work from the repository root.
Read AGENTS.md only if you need repository routing context.
Read .github/skills/writing-style-review/SKILL.md only when changing prose around links.
For Learning Paths, read .github/skills/learning-path-structure-review/SKILL.md when link placement or further_reading is involved.

Workflow

Identify the target file, directory, section, or selected text. If you've previously read the page, use context and don't re-read it unless there's a change since the last read.
Read surrounding context before suggesting any changes.
After understanding the context of the URL, suggest concise and natural rewrites to the anchor text based on Quality rules.
After the user accepts suggestions, make changes, then re-open or search changed lines to verify the Markdown link syntax is valid.
After you make changes, report changed links and any links not verified.

Quality rules

Link text should make sense without nearby words when possible.
Prefer destination-specific anchors such as Docker install guide, Arm Developer resources, or Google Cloud firewall rules.
Avoid anchors that only describe the mechanic, such as here, click here, this page, read more, link, or website, as well as bare URLs or repeated generic text.
Avoid overlong anchors that wrap a whole sentence.
Don't change product names, tool names, URLs, or technical meaning to satisfy prose preferences.
Don't add speculative links. Verify internal targets or state when verification was not possible. Preserve the URL unless it's broken or the user asks for a change.

Examples

Use these examples for both link format and link text guidance.

Poor:

See [here](/install-guides/docker/) for setup.

Better:

For setup instructions, see the [Docker install guide](/install-guides/docker/).

Poor:

A list of all AWS instance types can be [viewed here](https://aws.amazon.com/ec2/instance-types/).

Better:

For a complete list, see [Amazon EC2 instance types](https://aws.amazon.com/ec2/instance-types/).

同仓库更多 Skills

同仓库

learning-path-structure-review

ArmDeveloperEcosystem/arm-learning-paths

Review Arm Learning Paths for structural soundness, task ownership, scope discipline, progression, validation, further reading placement, recap sections, and performance-learning integrity. Use when asked to review, create, reorganize, or assess the structure of content under content/learning-paths.

2026-07-15146

seo-geo-aeo-review

ArmDeveloperEcosystem/arm-learning-paths

Review and improve Arm Learning Paths and install guides for SEO, GEO, AEO, search snippets, AI-agent selection, and answer-engine readiness. Use when asked to optimize discoverability, search intent, AI-readable structure, page titles, headings, summaries, or content selection signals beyond only front matter descriptions.

2026-07-15146

writing-style-review

ArmDeveloperEcosystem/arm-learning-paths

Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides. Use when asked to polish prose, make content less AI-generated, improve clarity, or align with Arm editorial style.

2026-07-15146

markdown-component-edit

ArmDeveloperEcosystem/arm-learning-paths

Add or update structured Markdown and Hugo components in Arm Learning Paths and install guides. Use when asked to turn selected text into a link, table, notice, tab pane, code pane, shortcode block, or other repo-specific Markdown component while preserving surrounding content.

2026-07-07146

draft-learning-path

ArmDeveloperEcosystem/arm-learning-paths

Toggle draft mode on a Learning Path _index.md. Use when: marking a learning path as draft, hiding a learning path from publication, adding draft: true to front matter, unpublishing or disabling a learning path, removing draft, publishing a learning path, taking a learning path out of draft.

2026-06-29146

code-sample-review

ArmDeveloperEcosystem/arm-learning-paths

Review and improve code samples, commands, command output, and fenced code blocks in Arm Learning Paths and install guides. Use when checking editorial formatting, technical accuracy, runnable commands, output lead-ins, code fence integrity, language tags, or token-heavy and unexplained code or output blocks.

2026-06-29146

name	link-text-review
description	Review and improve accessible Markdown link text in Arm Learning Paths and install guides. Use when asked to find vague links, fix link text such as here or click here, verify internal links, improve screen-reader clarity, or make links descriptive and task-focused.

Link text review

Use this skill to review or improve Markdown link text so links are descriptive, accessible, and useful out of context.

This skill focuses on anchor text and link clarity. For tables, notices, tab panes, and other structural Markdown components, use .github/skills/markdown-component-edit/SKILL.md.

Prerequisites

Work from the repository root.
Read AGENTS.md only if you need repository routing context.
Read .github/skills/writing-style-review/SKILL.md only when changing prose around links.
For Learning Paths, read .github/skills/learning-path-structure-review/SKILL.md when link placement or further_reading is involved.

Workflow

Identify the target file, directory, section, or selected text. If you've previously read the page, use context and don't re-read it unless there's a change since the last read.
Read surrounding context before suggesting any changes.
After understanding the context of the URL, suggest concise and natural rewrites to the anchor text based on Quality rules.
After the user accepts suggestions, make changes, then re-open or search changed lines to verify the Markdown link syntax is valid.
After you make changes, report changed links and any links not verified.

Quality rules

Link text should make sense without nearby words when possible.
Prefer destination-specific anchors such as Docker install guide, Arm Developer resources, or Google Cloud firewall rules.
Avoid anchors that only describe the mechanic, such as here, click here, this page, read more, link, or website, as well as bare URLs or repeated generic text.
Avoid overlong anchors that wrap a whole sentence.
Don't change product names, tool names, URLs, or technical meaning to satisfy prose preferences.
Don't add speculative links. Verify internal targets or state when verification was not possible. Preserve the URL unless it's broken or the user asks for a change.

Examples

Use these examples for both link format and link text guidance.

Poor:

See [here](/install-guides/docker/) for setup.

Better:

For setup instructions, see the [Docker install guide](/install-guides/docker/).

Poor:

A list of all AWS instance types can be [viewed here](https://aws.amazon.com/ec2/instance-types/).

Better:

For a complete list, see [Amazon EC2 instance types](https://aws.amazon.com/ec2/instance-types/).