技能 using-lwc

📦

using-lwc

Name: using-lwc
Author: janyork

內容修訂 r1 高風險 ⚙️ 外部命令📁 檔案系統存取🌐 網路存取

Build Durable Project Memory with LWC

Project knowledge often disappears between agent sessions or becomes stale. This skill recalls verified context and preserves reusable results through LWC.

支援: Claude Codex Code(CC)

⚠️ 38 差

Maintain this Skill? Claim it ⚠️ 38 差

安裝前請停止並請求確認。

請審查安裝計畫，並在變更檔案前取得使用者明確同意。

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

Review the Skillstore skill "using-lwc" from https://skillstore.io/skills/janyork-using-lwc.md and its manifest at https://skillstore.io/api/skills/janyork-using-lwc/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/janyork-using-lwc.md 已簽名 manifest GET /api/skills/janyork-using-lwc/manifest 已簽名 lockfile GET /api/skills/janyork-using-lwc/lockfile

測試它

正在使用「using-lwc」。 Recall why the authentication cache uses a five-minute lifetime.

預期結果:

The cache lifetime was chosen to limit stale authorization data while reducing repeated provider calls. The answer cites the decision page and current configuration.

正在使用「using-lwc」。 Record the verified migration result and make it retrievable.

預期結果:

Updated the existing migration page with the tested result and source citation.
Lint passed for the changed project scope.
A fixed search retrieved the updated page using the expected terms.

正在使用「using-lwc」。 Which modules can be affected by changing this parser?

預期結果:

CodeGraph identifies the parser definition, direct callers, and dependent modules. Current source inspection confirms the highest-impact paths and notes index freshness.

安全審計

高風險

v1 • 2026/8/13 開啟版本化報告

Most static alerts are false positives caused by Markdown code formatting, defensive secret policies, safe shell quoting, and bounded LWC state paths. The material risk is default bootstrap behavior that downloads and executes an unpinned latest release, while also creating persistent user-level LWC state.

已掃描檔案

2,397

分析行數

複核項目

已忽略的誤報

已確認的安全問題 (1)

高

SKILL.md:29-30 scripts/bootstrap.sh:160-164 scripts/install-lwc.sh:55-67 scripts/install-lwc.sh:111-149

Automatic Installation Executes an Unpinned Remote Release

The default bootstrap downloads the latest LWC release and executes it without explicit installation consent. Checksums come from the same mutable GitHub release, so repository compromise can execute code in the agent context.

The control flow defaults LWC_AUTO_INSTALL to enabled, fetches the latest release and its checksum from one remote source, then runs the downloaded executable.

能力複核項目 (9)

這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。

高

scripts/install-lwc.sh:148

Shell command substitution

[ "$("$downloaded_binary" --version 2>/dev/null || true)" = "lwc ${version}" ] ||

The installer executes the newly downloaded binary for a version check. Its checksum comes from the same mutable release source, so compromise of that source can produce code execution.

中

scripts/bootstrap.sh:163

Hidden file access

LWC_INSTALL_DIR="$home_dir/.local/bin" sh "$installer" >&2 ||

Bootstrap invokes the bundled installer with a destination under ~/.local/bin when no compatible LWC is found. This is a real persistent filesystem modification performed by the default workflow.

中

scripts/bootstrap.sh:176

Hidden file access

global_wiki="$home_dir/.lwc/wiki.db"

The path is used as the global LWC database, and later initialization creates persistent state under ~/.lwc. This is expected functionality but changes user-level data outside the project.

中

scripts/bootstrap.sh:177

Hidden file access

global_policy_state="$home_dir/.lwc/.using-lwc-bootstrap-v1"

This hidden state path is written with pending and complete markers during global initialization. The write is intentional, persistent, and outside the active project.

中

scripts/install-lwc.sh:56

Shell command substitution

effective_url="$(curl -fsSLI -o /dev/null -w '%{url_effective}' "$latest_url")" ||

The substitution runs curl against GitHub and follows redirects to select the latest release. The arguments are fixed, but this is a real network-dependent external command.

中

scripts/install-lwc.sh:79

Hidden file access

install_dir="$HOME/.local/bin"

The installer defaults to placing an executable in ~/.local/bin. This is an intentional persistent change to a user executable directory.

中

scripts/install-lwc.sh:154

Hidden file access

staged_binary="$install_dir/.lwc.install.$$"

The downloaded executable is staged as a hidden file in the install directory before replacing the destination. The operation is controlled but modifies a persistent executable location.

低

scripts/install-lwc.sh:55

Hardcoded URL

latest_url="https://github.com/${repository}/releases/latest"

The installer contacts a hardcoded GitHub latest-release endpoint. The destination is expected and HTTPS-protected, but it is still an external network dependency.

低

scripts/install-lwc.sh:67

Hardcoded URL

release_url="https://github.com/${repository}/releases/download/${tag}"

This URL is the hardcoded GitHub base used to download release archives and checksums. It is legitimate project infrastructure, but installation depends on remote content.

風險因素

⚙️ 外部命令 (50)

📁 檔案系統存取 (44)

🌐 網路存取 (2)

scripts/install-lwc.sh:55 scripts/install-lwc.sh:67

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/janyork-using-lwc/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/janyork-using-lwc/security.svg)](https://skillstore.io/skills/janyork-using-lwc?utm_source=security_passport_badge)

HTML 徽章

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

嵌入卡片

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

學術引用 (APA · BibTeX · CFF)

APA 引用

janyork. (2026). using-lwc security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/janyork-using-lwc/audits/1

BibTeX 引用

@techreport{janyork-janyork-using-lwc-2026,
  author = {janyork},
  title = {using-lwc security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/janyork-using-lwc/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "using-lwc security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "janyork"
date-released: "2026-08-13"
url: "https://skillstore.io/skills/janyork-using-lwc/audits/1"
identifiers:
  - type: other
    value: "skillstore:janyork-using-lwc:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

Continue Long Development Work

Recall prior decisions, verified findings, and code relationships before continuing a complex implementation.

Preserve Research Evidence

Ingest authoritative documents, retain citations, and update durable conclusions after source verification.

Recover Project Context

Restore bounded project knowledge after compaction, interruption, or a failed maintenance operation.

試試這些提示

Recall Project Context

Use LWC to recall the most relevant verified context for this project. Summarize prior decisions and cite the pages used.

Preserve a Verified Decision

Review this completed decision and its evidence. Update the appropriate LWC page, preserve citations, then verify retrieval.

Analyze Structural Impact

Use the current CodeGraph to identify definitions, callers, dependencies, and likely impact for this change. Verify important claims against checked-out code.

Repair and Validate Memory

Inspect the failed LWC work and affected scope. Recover safely, resolve conflicts, lint changes, and run fixed retrieval checks before reporting completion.

最佳實務

Recall once, then open only the pages and sources needed to verify the current task.
Treat stored pages as durable leads and verify implementation claims against current code.
Write only verified reusable knowledge, then lint and test retrieval.

避免

Do not store passwords, tokens, private keys, raw reasoning, or unverified guesses.
Do not widen the authorized project root to locate another Wiki.
Do not edit LWC databases, graph sidecars, or generated projections directly.