sg-veille

Triage external links and incoming information before they dissolve into random browser tabs.

A governance-aware link-analysis skill for reviewing URLs or pasted content, summarizing relevance, and routing follow-up actions.

Browse skills on GitHub Back to the hub

Problem

What problem this solves

Useful external information often gets consumed passively instead of being sorted into ignore, backlog, content, or deeper investigation.

Outcome

What changes when it works

You get a more intentional triage layer between incoming information, project-local governance context, and actual product or content decisions.

Why It Matters

What this changes for a solo founder

This skill matters when your research intake is bigger than your working memory. It converts reading into a clearer action surface. It also helps spot when product claims, declared products, or public routes need governance before anything is repurposed.

When to use it

When you have links or pasted content to review
When market or product signals need structured triage
When a source may affect the product inventory, public claims, or sales surfaces
When you want to turn reading into a bounded decision or a clear owner handoff

What you give it

One or more URLs or pasted source material
The current project or business context

What you get back

A relevance-oriented summary
Source-specific options and an explicit decision before any durable follow-up
Project-local governance context checks before scoring
sg-content repurpose handoffs or surface-missing findings for public-content ideas
Explicit callouts when a source touches declared products or proof-backed claims
Less information sprawl in your workflow

Typical examples

/sg-veille https://example.com/article
/sg-veille these five competitor pages
/sg-veille pasted notes from founder forum

Limits

It helps triage incoming information; it does not replace deeper market or product research, content production, documentation work, or tracker maintenance
The quality of the outcome depends on the relevance of the inputs you feed it
It should not invent blog, newsletter, or social surfaces that are not declared in the project's content map

Related Skills

See the rest of the loop around this move.

Research & Grow

sg-content

Manage content work through one lifecycle instead of guessing which writing, audit, docs, or SEO skill to launch.

A master content lifecycle skill for routing strategy, repurposing, drafting, enrichment, audits, public-content governance, validation, and ship readiness through the right owner skills.

Open skill page

Research & Grow

sg-research

Research a topic deeply enough that you can make a better product or GTM decision afterward.

A structured research skill for gathering evidence, checking current-source freshness, and saving reusable workflow reports.

Open skill page

Research & Grow

sg-marketing

Choose the right marketing review without choosing among four overlapping skills.

One marketing skill with explicit modes for market evidence, GTM readiness, copy clarity, and persuasion.

Open skill page

Plan & Decide

sg-backlog

Capture ideas without letting them hijack the current execution thread.

A local-first backlog management skill for parking non-urgent work while keeping active delivery focused.

Open skill page

Go Deeper

This public page explains the move. The repository explains the execution contract.

Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.

Documentation Overview Open skills on GitHub Return to the skills hub