Skills lark-vc

📦

lark-vc

Name: lark-vc
Author: larksuite

v1.0.0 Content revision r2 Medium Risk 📁 Filesystem access⚙️ External commands

Search and Review Lark Video Meetings

Finding reliable records across completed Lark meetings can require several tools and identifiers. This skill routes searches, participant checks, transcripts, notes, and recordings through lark-cli.

Supports: Claude Codex Code(CC)

📊 70 Adequate

This skill is part of a pack

Install the whole pack to get every skill the task needs, in one command.

Meeting Follow-Up Kit · 3 skills Install whole pack

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "lark-vc" from https://skillstore.io/skills/larksuite-lark-vc.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-vc/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/larksuite-lark-vc.md Signed manifest GET /api/skills/larksuite-lark-vc/manifest Signed lockfile GET /api/skills/larksuite-lark-vc/lockfile

Test it

Using "lark-vc". Find completed Atlas reviews from last week.

Expected outcome:

Three completed meetings matched the date range and Atlas keyword.
Each result includes its date, organizer, participants, and available artifacts.
Two meetings have transcripts; one has only participant and title data.

Using "lark-vc". Who attended the selected launch review?

Expected outcome:

The authorized participant snapshot lists eight attendees.
Six attendees have join and leave times; two have only attendance records.

Using "lark-vc". Summarize decisions and actions from this meeting.

Expected outcome:

The transcript supports three decisions and four assigned actions.
Each action includes its owner and deadline when stated.
Unresolved questions are separated from confirmed decisions.

Security Audit

Medium Risk

v5 • 7/23/2026 Open versioned report

One static finding is confirmed because SKILL.md mandates loading instructions from outside the audited package; the other 129 detections are syntax false positives. A separate medium finding covers live bot join guidance inside the read-only historical search reference. No encoded payload, host reconnaissance, credential theft, or data exfiltration was found.

Files scanned

754

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

references/lark-vc-search.md:83-91

Out-of-Scope Live Meeting Control Guidance

The historical search reference states that bots can join multiple live meetings and directs continued join or leave actions. This conflicts with its read-only scope.

Lines 83-91 explicitly describe live bot participation inside documentation for a read-only historical meeting search command.

Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

SKILL.md:13

Path traversal sequence

**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md),其中包含认证、权限处理*

SKILL.md line 13 mandates reading ../lark-shared/SKILL.md outside the audited package. Changes there can alter agent instructions without changing this skill's audited content.

Risk Factors

📁 Filesystem access (43)

⚙️ External commands (50)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/larksuite-lark-vc/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/larksuite-lark-vc/security.svg)](https://skillstore.io/skills/larksuite-lark-vc?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/larksuite-lark-vc?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-vc/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/larksuite-lark-vc.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

larksuite. (2026). lark-vc security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-vc/audits/5

BibTeX citation

@techreport{larksuite-larksuite-lark-vc-2026,
  author = {larksuite},
  title = {lark-vc security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/larksuite-lark-vc/audits/5},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-vc security audit report (audit version 5)"
version: "1.0.0"
type: report
authors:
  - name: "larksuite"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/larksuite-lark-vc/audits/5"
identifiers:
  - type: other
    value: "skillstore:larksuite-lark-vc:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Review Project Decisions

Find a completed project meeting and summarize decisions, unresolved points, and assigned actions from its transcript.

Verify Meeting Attendance

Retrieve an authorized participant snapshot and identify who attended a completed meeting.

Collect Meeting Artifacts

Locate notes, transcript links, recording details, summaries, tasks, and chapters for a selected meeting.

Try These Prompts

Find a Completed Meeting

Find my completed Lark meetings about [topic] between [start date] and [end date]. Show the date, organizer, and participants.

Check Participants

For the completed meeting [meeting name or ID], list the participant snapshot and note each available join or leave time.

Retrieve Meeting Artifacts

Find [meeting name], then return available note, transcript, recording, summary, task, and chapter links without downloading media.

Analyze a Full Meeting Set

Search all completed [project] meetings during [period], follow every page, and compare transcript evidence for decisions, owners, deadlines, and unresolved issues.

Best Practices

Provide a date range, participant, organizer, room, or genuine meeting keyword.
Confirm the intended meeting when several search results have similar titles.
Use transcript evidence for independent analysis and request AI summaries only when needed.

Avoid

Do not use historical meeting search for future schedules.
Do not assume the first result page contains every matching meeting.
Do not expose meeting identifiers, tokens, transcripts, or participant data beyond the intended audience.