Skip to content
Back to skills

Browser Screenshot Capture

ASecurity

Capture browser-based evidence for AML review in a way that is reproducible and human-reviewable.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 30, 2026
devops

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 30, 2026

npx -y skills add tomcustos/tcaml-framework --skill browser-screenshot-capture --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Browser Screenshot Capture?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Browser Screenshot Capture
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomcustos-browser-screenshot-capture/badge)](https://www.skillsdirectory.com/skills/tomcustos-browser-screenshot-capture)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
tcaml_version: "1.8.1"
document_type: "skill"
skill_type: "connector"
skill_id: "browser-screenshot-capture"
title: "Browser Screenshot Capture Connector Skill"
risk_area:
  - evidence
human_review_required: true
final_decision_allowed: false
paid_source_boundary: false
source_access_required: "not_applicable"
private_configuration_required_for:
  - client-specific Implementation Profiles
  - private source configuration
  - evidence rules
  - MLRO escalation logic
---
# Browser Screenshot Capture Connector Skill

## Purpose

Capture browser-based evidence for AML review in a way that is reproducible and human-reviewable.

## When to Use

Use when an AML workflow requires a visual record of a web page, search result, registry page, sanctions result, adverse media result, website page, domain lookup or source document.

## Required Inputs

- case identifier;
- subject under review;
- source URL or page title;
- reason for capture;
- output folder;
- date/time if available.

## Workflow

1. Verify that the page relates to the correct subject or source query.
2. Capture the visible page area required by policy.
3. If the result spans multiple pages, capture each material page separately.
4. Ensure the URL/address bar or source identifier is visible where technically possible.
5. Save the screenshot using the implementation profile naming rule.
6. Add an entry to the evidence log.
7. Mark whether the capture is complete, partial or limited.

## Evidence Metadata

Record:

- source name;
- URL or source identifier;
- access date;
- query/search term;
- screenshot file name;
- evidence quality label;
- limitations.

## Red Flag Routing

The screenshot connector does not decide whether a finding is material. If the captured page contains a red flag under the selected AML skill or implementation profile, route the case to manual review.

## Agent Must Not

- crop out material context;
- edit or enhance evidence in a way that changes meaning;
- summarize a screenshot as a final compliance decision;
- omit visible uncertainty.

Files in this skill

  • SKILL.md2 KB
  • WORKFLOW.md381 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…