#215 scrape-webpage: add page-import pipeline guard + Use-this-when trigger - #245
Conversation
Tessl Skill Lint
|
trieloff
added
the
ai-generated
There was a problem hiding this comment.
Pull request overview
This PR updates the scrape-webpage skill’s frontmatter description to improve routing behavior: it now leads with an explicit “Use this when …” trigger and clearly indicates it is an internal page-import pipeline step that should not be invoked directly.
Changes:
- Rewrites the
scrape-webpagedescriptionto start with “Use this when …” trigger language. - Adds an explicit guard: “Do not invoke directly — called by page-import as a pipeline step.”
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Addresses #215.
Problem —
scrape-webpage's description opened with what it does, not when to invoke it, and gave no signal that it is apage-importpipeline step — so an agent could load it in isolation or skip it when routing.Solution — Rewrote the description to lead with a
Use this when …trigger and added an explicitDo not invoke directly — called by page-importguard, per the issue's recommendation for pipeline sub-skills. Content-only change to the frontmatterdescription.Validated with
npm run validate. Generated with AI assistance.Pull Request opened by Augment Code | View session