skills nits

Author: anupras-mohapatra-arm

.github/skills/learning-path-structure-review/SKILL.md

@@ -10,7 +10,7 @@ Use this skill when a Learning Path needs a structural review. Focus on whether
 ## Workflow
 
 1. Identify the Learning Path directory and read the relevant Markdown files together.
-2. State the owned developer task in one sentence. If the task is unclear, too broad, or split across unrelated goals, flag it.
+2. Summarize the developer task owned by LP in one sentence. If the task is unclear, too broad, or split across unrelated goals, flag it.
 3. Check the required file shape:
    - The Learning Path has an `_index.md` file.
    - The Learning Path has an `_next-steps.md` file.

.github/skills/seo-geo-aeo-review/SKILL.md

@@ -23,9 +23,11 @@ For focused front matter `description` edits only, use `.github/skills/metadata-
 
 ## Workflow
 
+On any given page:
+
 1. Identify the target content type and target developer intent. 
-2. Read the title, front matter description, headings, introduction, prerequisites, main task flow, validation, conclusion, and further reading. If you've previously read a page, use context and don't re-read it unless there's a change since the last read. 
-3. State the page's owned task in one sentence. If the task is unclear or too broad, flag it.
+2. Read the title, front matter description, headings, introduction, prerequisites, main task flow, validation, conclusion, and further reading. If you've previously read the page, use context and don't re-read it unless asked to. 
+3. Summarize the page's owned task in one sentence. If the task is unclear or too broad, flag it.
 4. Review SEO signals:
    - The title is task-led and includes the main technology, platform, or tool.
    - The `description` is one concise sentence that states the task, context, and outcome.

.github/skills/writing-style-review/SKILL.md

@@ -10,10 +10,10 @@ Use this skill for granular prose, voice, readability, terminology, and style re
 ## Workflow
 
 1. Identify the target file, section, or selected text.
-2. Read surrounding context so style edits preserve the author's intent and the technical flow. If you've previously read the page, use context and don't re-read it unless there's a change since the last read. 
+2. Read surrounding context so style edits preserve the author's intent and the technical flow. If you've previously read the page, use context and don't re-read it unless asked to. 
 3. Review the target against the guidelines defined in this skill.
 4. Depending on request type, do the following:
-  - For review requests, report high-impact style issues by file and line when possible. 
+  - For review requests, report style issues by file and line when possible, ordered by severity. 
   - For edit requests, make focused rewrites, then re-open changed sections to check Markdown, shortcodes, links, and code fences.
 
 ## Voice and tone