fix(skills): strip leaked XML tags from skill tails; clarify lint:check has no per-file target

Removes stray </content>/</invoke> markup that leaked into add-block,
add-connector, add-hosted-key canonical skills, and reword the cleanup
skill's lint step to note bun run lint:check runs repo-wide via turbo
(no per-path API). Projections regenerated via skills:sync.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QjefwescJoHZ6zcc3C17FR

Author: TheodoreSpeaks

.agents/skills/add-block/SKILL.md

@@ -889,4 +889,3 @@ After creating the block, you MUST validate it against every tool it references:
 3. **Verify block outputs** cover the key fields returned by all tools
 4. **Verify conditions** — each subBlock should only show for the operations that actually use it
 5. **Verify `{Service}BlockMeta` is exported** with at least 7 templates, each having `icon`, `title`, `prompt`, `modules`, `category`, and `tags`
-</content>

.agents/skills/add-connector/SKILL.md

@@ -624,4 +624,3 @@ export const CONNECTOR_META_REGISTRY: ConnectorMetaRegistry = {
 - [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
 - [ ] Registered the full connector in `connectors/registry.server.ts`
 - [ ] Registered the meta in `connectors/registry.ts` (same alphabetical-by-id ordering as registry.server.ts)
-</content>

.agents/skills/add-hosted-key/SKILL.md

@@ -300,5 +300,3 @@ This summary helps reviewers verify that the pricing and rate limiting are well-
 - [ ] Provider entry added to the BYOK settings UI with icon and description
 - [ ] Env vars documented: `{PREFIX}_COUNT` and `{PREFIX}_1..N`
 - [ ] Pricing and throttling summary provided to reviewer
-</content>
-</invoke>

.agents/skills/cleanup/SKILL.md

@@ -51,7 +51,7 @@ Comments apply last, on purpose: that pass operates on whatever the earlier stru
 2. If the `old_string` still matches verbatim, apply it — a content-anchored edit is safe even if its line moved.
 3. If it no longer matches (an earlier pass altered that region), do **not** force the stale patch. Re-derive the change from the current code by re-applying that pass's rule to the construct, or drop it if a prior pass already made it moot. Never apply a proposal against text it wasn't computed from.
 
-After all edits, run `bun run lint:check` on the touched files.
+After all edits, run `bun run lint:check` (it runs `turbo run lint:check` across the repo — there is no per-file target, so run the full check).
 
 ## Step 4 — Summary
 

.claude/commands/add-block.md

@@ -888,4 +888,3 @@ After creating the block, you MUST validate it against every tool it references:
 3. **Verify block outputs** cover the key fields returned by all tools
 4. **Verify conditions** — each subBlock should only show for the operations that actually use it
 5. **Verify `{Service}BlockMeta` is exported** with at least 7 templates, each having `icon`, `title`, `prompt`, `modules`, `category`, and `tags`
-</content>

.claude/commands/add-connector.md

@@ -623,4 +623,3 @@ export const CONNECTOR_META_REGISTRY: ConnectorMetaRegistry = {
 - [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
 - [ ] Registered the full connector in `connectors/registry.server.ts`
 - [ ] Registered the meta in `connectors/registry.ts` (same alphabetical-by-id ordering as registry.server.ts)
-</content>

.claude/commands/add-hosted-key.md

@@ -299,5 +299,3 @@ This summary helps reviewers verify that the pricing and rate limiting are well-
 - [ ] Provider entry added to the BYOK settings UI with icon and description
 - [ ] Env vars documented: `{PREFIX}_COUNT` and `{PREFIX}_1..N`
 - [ ] Pricing and throttling summary provided to reviewer
-</content>
-</invoke>

.claude/commands/cleanup.md

@@ -50,7 +50,7 @@ Comments apply last, on purpose: that pass operates on whatever the earlier stru
 2. If the `old_string` still matches verbatim, apply it — a content-anchored edit is safe even if its line moved.
 3. If it no longer matches (an earlier pass altered that region), do **not** force the stale patch. Re-derive the change from the current code by re-applying that pass's rule to the construct, or drop it if a prior pass already made it moot. Never apply a proposal against text it wasn't computed from.
 
-After all edits, run `bun run lint:check` on the touched files.
+After all edits, run `bun run lint:check` (it runs `turbo run lint:check` across the repo — there is no per-file target, so run the full check).
 
 ## Step 4 — Summary
 

.cursor/commands/add-block.md

@@ -883,4 +883,3 @@ After creating the block, you MUST validate it against every tool it references:
 3. **Verify block outputs** cover the key fields returned by all tools
 4. **Verify conditions** — each subBlock should only show for the operations that actually use it
 5. **Verify `{Service}BlockMeta` is exported** with at least 7 templates, each having `icon`, `title`, `prompt`, `modules`, `category`, and `tags`
-</content>

.cursor/commands/add-connector.md

@@ -618,4 +618,3 @@ export const CONNECTOR_META_REGISTRY: ConnectorMetaRegistry = {
 - [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
 - [ ] Registered the full connector in `connectors/registry.server.ts`
 - [ ] Registered the meta in `connectors/registry.ts` (same alphabetical-by-id ordering as registry.server.ts)
-</content>