feat: improve skill score for acquia-source-canvas-pages

[yogesh-tessl]

Hey @balintbrews 👋

truly impressive work. 24 skills for Canvas components, and they're clearly structured around real developer workflows. The breakdown from component definition to composability to design decomposition shows you've mapped the whole lifecycle.

I ran your skills through tessl skill review at work and found some targeted improvements for acquia-source-canvas-pages. It had the most headroom of all 24 skills in the repo. Here's the before/after:

Skill	Before	After	Change
acquia-source-canvas-pages	59%	88%	+29%

Changes made

Description improvements (biggest impact - 40% → 100%):

• Rewrote the frontmatter description from a fragmented keyword list ("images, props, layout") into full action phrases ("creates pages, places components, configures layout and props, wires image media, publishes drafts")
• Added an explicit "Use when..." clause with natural trigger terms users would actually say ("publish a Canvas page", "deploy page changes to Source", "update remote page layout")
• Added clear scope exclusions ("Does not cover local Workbench preview or CLI component pushes") to prevent misrouting
• Switched description format from YAML chevron to quoted string for standard frontmatter

Content improvements (57% → 70%):

• Consolidated the repeated "canvas push/pull don't sync page JSON" messaging (was stated 3 times across sections) into a single prominent blockquote constraint at the top
• Added a concrete JSON example for update_component_props showing how to wire a Drupal media reference (target_id) to a hero image prop
• Added an explicit validation checkpoint (step 4) to the MCP workflow: re-fetch layout and verify all instances present and image props resolve to non-null URLs before publishing
• Workflow clarity improved from outline to a gated sequence (discover → create → place → validate → publish)

---

quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.

if you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.

[acquia-stalebot-platauto]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please remove the stale label to avoid it being closed. Thank you for your contributions. More info: https://github.com/acquia/devops-github-administration/blob/main/docs/operations_related_to_repositories.md#acquia-stale-bot

[yogesh-tessl]

@balintbrews, just a heads up that the stale bot flagged this. The main change here is pretty small.

The acquia-source-canvas-pages description had fragmented keywords that weren't matching well, and the MCP workflow was missing a validation step before publish. Happy to adjust anything if the direction is off.
No rush on this. Just didn't want it to auto-close without you getting a chance to look.

[yogesh-tessl]

hey @balintbrews 👋, just a friendly follow-up in case this got buried, happy to help move it forward!
Totally fine if there's a process, just wanted to keep it visible.