Byted Las Document Parse

v1.0.0

CRITICAL: EXCELLENT at parsing BOTH PDF documents and IMAGES (including LONG SCREENSHOTS, scanned documents, and standard images). Extract structured Markdow...

0· 64·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The requested credentials (LAS_API_KEY as primary, and TOS_ACCESS_KEY / TOS_SECRET_KEY / TOS_BUCKET for uploading local files) match the stated purpose of calling a Bytedance LAS parsing API and uploading/downloading artifacts to TOS. The code calls LAS endpoints and uses a TOS SDK for uploads, which is coherent with the description. Minor mismatch: documentation says TOS_BUCKET can be optional (overridable via --tos-bucket), but the registry metadata lists it as required; this is a small config inconsistency but not malicious.
!
Instruction Scope
The SKILL.md + scripts instruct the agent to automatically trigger on any shared local file path, URL, or tos:// path and to auto-load env.sh files (skill dir and current working directory). Auto-loading env.sh from the current working directory means the skill may read environment values from a project/workspace that contain unrelated secrets. The skill also allows a user-provided --env-file that will force-overwrite environment variables. These behaviors are functional for local file uploads but increase the chance of the skill reading/using environment variables beyond the minimal set needed for a single parse operation.
Install Mechanism
There is no remote download/install spec embedded in the skill bundle; dependencies are declared in requirements.txt and the SKILL.md instructs creation of a virtualenv and pip install -r requirements.txt — a standard, low-risk installation pattern. No suspicious external URLs or archive extract operations were used in install instructions.
Credentials
Requested environment variables (LAS_API_KEY, TOS_ACCESS_KEY, TOS_SECRET_KEY, TOS_BUCKET) are reasonable for a parser that uploads local files to TOS and calls LAS. However, the skill's auto-detection of env.sh files in cwd and the ability for an explicit --env-file to forcibly overwrite existing environment variables increase risk of unintentional use of unrelated secrets. Also, registry metadata marking TOS_BUCKET as required while docs treat it as optional is a minor inconsistency to be aware of.
Persistence & Privilege
The skill is not marked always:true and does not request modification of other skills or system-wide configuration. It runs subprocesses and writes results to /tmp (and optionally uploads a ZIP to TOS), which is expected for this functionality. Autonomous invocation is allowed (platform default) but not combined with an elevated 'always' privilege.
Assessment
This skill generally appears to do what it says: call a LAS API to parse PDFs/images and optionally upload/download results via TOS. Before installing, consider the following: - Secrets required: you must provide LAS_API_KEY and (for local-file uploads) TOS_ACCESS_KEY / TOS_SECRET_KEY and a TOS_BUCKET. Only supply credentials you trust and prefer creating a dedicated, least-privilege LAS/TOS keypair and bucket for this skill. - env.sh auto-load: the skill auto-loads env.sh from the skill directory and from the current working directory (and a user-specified --env-file will forcibly overwrite env vars). Make sure there is no sensitive env.sh in the working directory that could be picked up accidentally (e.g., CI keys, cloud credentials). Prefer using a minimal env.sh containing only the keys needed for this skill. - Automatic triggers: SKILL.md says to trigger whenever the user shares a local path/URL/tos:// path. If you want explicit consent before parsing local files, disable automatic triggers in your agent or only invoke the skill manually. - Data flow: the skill downloads remote images, saves files to /tmp, creates ZIP archives, and may upload archives to your TOS bucket and generate presigned download URLs. Review who has access to the TOS bucket and the lifetime of presigned URLs. - Review permissions: give the TOS credentials only the permissions required to write the expected result key/prefix, and rotate keys if you stop using the skill. If you want to increase confidence further, you can: (1) inspect scripts locally (they are included) to verify behavior, (2) run the skill in an isolated environment/container, and (3) create dedicated minimal-permission API/TOS credentials for it.

Like a lobster shell, security has layers — review code before you run it.

latestvk970wqgae5v1qgf1zc0j63wfr983m2s9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

EnvLAS_API_KEY, TOS_ACCESS_KEY, TOS_SECRET_KEY, TOS_BUCKET
Primary envLAS_API_KEY

Comments