acquisition-graduation

Convert repeated browser acquisition successes into reusable source acquisition guidance.

43|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/buriedsignals/spotlight --skill acquisition-graduation-buriedsignals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acquisition-graduation
Source: https://github.com/buriedsignals/spotlight/tree/main/skills/acquisition-graduation
Command: npx skills add https://github.com/buriedsignals/spotlight --skill acquisition-graduation-buriedsignals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During OSINT investigations, browser-based source acquisitions that work repeatedly are often lost or re-derived from scratch each time. This Skill captures those proven acquisition paths as durable, reusable documentation without storing secrets, cookies, or fragile session state. ## Core Features & Use Cases - Graduation Criteria Enforcement: Only promotes acquisition paths that are repeatable, deterministic, legally sound, and free of secrets or session artifacts. - Structured Knowledge Capture: Records source/domain, URL patterns, selectors, CDP/network observations, validation checks, and legal/rate-limit notes. - Explicit Exclusions: Blocks storage of passwords, tokens, CAPTCHA bypasses, personal accounts, and access-control evasion instructions. - Use Case: After a dev-browser session reliably extracts data from a public records portal twice, use this Skill to write a reusable acquisition note under skills/integrations/references/acquisition-paths/ so future cases follow the same validated path. ## Quick Start Use the acquisition-graduation skill to document the repeated browser acquisition path for this source as a reusable reference note.

Frequently Asked Questions about acquisition-graduation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a reusable browser acquisition path?

Record the source/domain, task class, URL patterns, selectors or CDP/network observations, waits and redirects, validation checks, and legal/rate-limit notes. Write the note under skills/integrations/references/acquisition-paths/{domain-or-source}.md.

When should an acquisition path be graduated into a reusable reference?

Graduate only when the source or domain class repeats, the URL or selector pattern is stable, success survived at least two attempts, validation checks can detect drift, and no secrets or session artifacts are required.

What information must never be stored in acquisition notes?

Never store passwords, cookies, bearer tokens, session IDs, personal accounts, CAPTCHA bypass paths, fragile pixel coordinates, or instructions to evade rate limits or access controls.

Can acquisition graduation handle one-off browsing sessions?

No. One-off browsing should not be graduated. The path must be likely to recur and validatable without brittle session state before it becomes durable guidance.

When should a new skill be proposed instead of expanding acquisition notes?

When an acquisition path becomes broad enough to deserve its own skill, propose a new skill rather than silently expanding the acquisition-graduation scope.