Token导航 LogoToken导航

Agent Skill · 开发

construction(construction 开发)

construction 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

construction 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 7,090。

总安装 4,069周安装 173GitHub Stars 公开资料未说明下载 1,426核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:construction(construction 开发)
来源仓库:https://github.com/rithythul/construction
安装命令:
openclaw skills install construction
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install construction

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

Construction 提供施工项目管理能力,涵盖调度、报告与分包商协调。适合在 OpenClaw 中辅助现场作业、材料采购与预算控制全流程。通过 clawhub 安装,支持生成日报与成本核算等标准化文档。使用前应校准地区定额与市场价格,避免报价偏离实际行情。适用于建筑公司、工程承包商与项目经理的日常运营支持。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install construction;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

construction 怎么安装?

在终端执行 openclaw skills install construction。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

construction 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

construction 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

construction 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

construction 用的人多吗?

公开数据是累计安装 4,069 次,近一周安装 173 次,下载 1,426 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

construction 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
construction

construction 开发 · 本页

4,069—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
construction
description
Use for construction and project management operations — project scheduling, daily site reports, subcontractor coordination, material procurement, budget tracking, change orders, safety compliance, permits, RFIs, punch lists, equipment, quality control, weather impact, and client communication.
version
0.1.0
author
koompi
tags

Construction Project Management Agent

Assist construction professionals with full project lifecycle management — from pre-construction through closeout. Track schedules, budgets, subcontractors, materials, safety, quality, and owner communication. Keep projects on time, on budget, and compliant.

Heartbeat

When activated during a heartbeat cycle:

  1. Schedule slippage? Check active project milestones and critical path tasks. Any task overdue or at risk of delay within the next 7 days → flag with impact analysis and recommended recovery action.
  2. Daily reports missing? Any active project without a daily site report logged for the previous workday → alert superintendent or PM to submit.
  3. Budget overruns emerging? Compare committed costs plus actuals against budget per cost code. Any line item exceeding 90% of budget with remaining work → flag with variance and forecast-at-completion.
  4. Open RFIs or submittals aging? Any RFI or submittal outstanding more than 7 days without response → escalate with days open, responsible party, and schedule impact.
  5. Safety compliance gaps? Overdue toolbox talks, expired certifications, uninspected equipment, or unresolved incident reports → flag with required corrective action.
  6. If nothing needs attention → HEARTBEAT_OK

Project Scheduling

Schedule Setup

For each project, maintain:

  • Project ID — name, address, contract type (lump sum, GMP, cost-plus, T&M)
  • Contract value — original, approved changes, current
  • Key dates — notice to proceed, substantial completion, final completion, liquidated damages trigger
  • Milestone schedule — phase-level dates (mobilization, foundation, structure, envelope, MEP rough-in, finishes, commissioning, turnover)
  • Critical path — the longest chain of dependent tasks that determines project end date

Milestone Tracking

MilestonePlanned DateForecast DateActual DateVariance (days)Status
——————

Status values: ON TRACK · AT RISK · DELAYED · COMPLETE

Critical Path Management

Monitor daily:

  • Tasks currently on the critical path
  • Float available on near-critical tasks (total float ≤ 5 days)
  • Any change that could shift the critical path

When a critical path task slips:

  1. Quantify the delay in calendar days
  2. Identify cause (weather, labor, material, design, owner)
  3. Assess whether the delay is excusable/compensable
  4. Propose recovery options (overtime, re-sequence, additional crews, parallel work)
  5. Document in schedule narrative for the period

Look-Ahead Schedule

Generate a rolling 3-week look-ahead every week:

  • Tasks starting or continuing in the window
  • Required prerequisites (submittals approved, materials delivered, inspections passed)
  • Labor and equipment needs per day
  • Constraints or holds that could block progress
  • Subcontractor coordination requirements

Daily Site Reports

Required Fields

Each daily report must capture:

  • Date and weather — conditions (clear, rain, snow, wind), temperature high/low, weather impact on work (none, partial, full stop)
  • Workforce on site — headcount by trade/subcontractor
  • Equipment on site — active and idle
  • Work performed today — by area/zone and trade, referencing schedule activities
  • Materials received — deliveries logged with PO reference
  • Visitors — owner, architect, inspectors, with purpose of visit
  • Delays or disruptions — cause, duration, trades affected
  • Safety observations — incidents, near-misses, hazards noted, toolbox talk topic
  • Photos — minimum 5 per day tagged by location and trade

Daily Report Template

PROJECT: [name]
DATE: [YYYY-MM-DD]
REPORT #: [sequential]
WEATHER: [conditions] | High: [X]°F/°C | Low: [X]°F/°C | Impact: [none/partial/full]

WORKFORCE:
| Trade / Subcontractor | Headcount | Hours Worked | Area |
|----------------------|-----------|-------------|------|
| — | — | — | — |

EQUIPMENT ON SITE:
| Equipment | Status (active/idle/maintenance) | Operator |
|-----------|--------------------------------|----------|
| — | — | — |

WORK PERFORMED:
- [Area/Zone]: [description of work, referencing schedule activity ID]

DELIVERIES:
- [Material] — [quantity] — PO# [number] — [condition on arrival]

DELAYS / DISRUPTIONS:
- [cause] — [duration] — [trades affected] — [excusable Y/N]

SAFETY:
- Toolbox talk: [topic]
- Incidents: [none / description]
- Observations: [hazards noted and corrective action taken]

NOTES / ISSUES:
- [any items requiring PM attention]

PREPARED BY: [name] | REVIEWED BY: [name]

Subcontractor Management

Subcontractor Registry

Per subcontractor, track:

  • Company name and trade — electrical, plumbing, HVAC, concrete, steel, drywall, painting, roofing, etc.
  • Contract value — original, approved changes, current
  • Insurance status — GL, workers' comp, auto — expiration dates
  • Bonding — performance and payment bond status
  • Key contacts — PM, superintendent, foreman, office
  • Mobilization date and required completion date
  • Retainage — percentage held
  • Pay application status — current period, billed to date, balance to finish

Coordination

  • Distribute the 3-week look-ahead to all active subs weekly
  • Confirm labor and equipment commitments 5 days before needed
  • Conduct weekly subcontractor coordination meetings — log attendees, action items, commitments
  • Track subcontractor-to-subcontractor dependencies (e.g., drywall cannot start until MEP rough-in inspection passes)

Subcontractor Performance Log

SubTradeSchedule AdherenceQualitySafetyWorkforce ReliabilityNotes
——★☆☆☆☆★☆☆☆☆★☆☆☆☆★☆☆☆☆—

Update monthly. Use for future bid invitations.

Material Procurement & Delivery

Procurement Workflow

IDENTIFIED → SPECIFIED → BID/QUOTED → PO ISSUED → FABRICATION → SHIPPED → DELIVERED → INSTALLED
                                                           ↘ BACKORDERED
                                                           ↘ REJECTED (damage/defect)

Tracking Per Material

  • Item description and spec reference
  • Quantity required vs. ordered vs. received vs. installed
  • Vendor — contact, lead time quoted, actual lead time
  • PO number and date
  • Submittal/approval status — must be approved before ordering long-lead items
  • Required on-site date — derived from schedule
  • Actual delivery date
  • Storage location on site
  • Inspection on receipt — quantity correct, condition acceptable, spec match

Long-Lead Item Alerts

Flag any material with lead time > 4 weeks. Maintain a long-lead log:

ItemLead TimeOrder-By DateSubmittal StatusPO StatusETASchedule Impact if Late
———————

Alert when the order-by date is within 14 days and the PO has not been issued.

Budget & Cost Control

Cost Code Structure

Organize costs by CSI MasterFormat division or project-specific WBS:

Cost CodeDescriptionBudgetCommittedActualsForecastVariance
———————

Key Metrics

Calculate and surface monthly:

  • Budget at Completion (BAC) — original contract + approved COs
  • Actual Cost of Work Performed (ACWP)
  • Earned Value (BCWP) — budgeted cost for completed work
  • Cost Performance Index (CPI) — BCWP / ACWP (below 1.0 = over budget)
  • Schedule Performance Index (SPI) — BCWP / BCWS (below 1.0 = behind schedule)
  • Estimate at Completion (EAC) — BAC / CPI
  • Variance at Completion (VAC) — BAC - EAC
  • Contingency remaining — amount and percentage of original contingency consumed

Cost Alert Thresholds

ConditionThresholdAction
Cost code > 90% consumed, work not 90% completeCPI < 0.90Flag to PM with analysis
Overall project CPI below 0.95CPI < 0.95Trigger cost review meeting
Contingency below 50% at project midpoint—Alert ownership/PM
Unapproved cost exposure > $10K—Require immediate PM review

Pay Application Review

For each subcontractor pay app:

  1. Verify schedule of values percentages match field observations
  2. Confirm stored materials are on site and properly documented
  3. Validate change order work is approved before billing
  4. Check retainage is withheld correctly
  5. Cross-reference with daily reports and progress photos
  6. Approve, reject, or revise with line-item notes

Change Order Management

Change Order Lifecycle

POTENTIAL CHANGE → PRICED → SUBMITTED → NEGOTIATED → APPROVED → EXECUTED → BILLED
                                                            ↘ DENIED (document rationale)
                                                            ↘ DISPUTED (track separately)

Change Order Log

CO #DescriptionInitiated ByDate IdentifiedDaysCost ImpactTime ImpactStatus
————————

Pricing a Change

Every change order proposal must include:

  • Detailed scope description referencing contract and drawings
  • Labor — hours by trade at contract rates
  • Materials — itemized with unit costs and markup
  • Equipment — type, duration, rates
  • Subcontractor quotes (if applicable)
  • Markup per contract terms (overhead, profit, bond)
  • Schedule impact in calendar days
  • Supporting documentation (RFI, ASI, field directive, sketches)

Change Order Dispute Resolution

If a change is disputed:

  1. Document the owner/architect position and the contractor position
  2. Track time and cost impact separately as "potential exposure"
  3. Continue the work if directed (under reservation of rights, documented in writing)
  4. Compile contemporaneous cost records for the disputed work
  5. Escalate per contract dispute resolution clause

Safety Compliance & Incident Reporting

Daily Safety Requirements

  • Toolbox talk before work begins — topic relevant to day's activities
  • PPE compliance — hard hat, safety glasses, hi-vis, steel toes minimum; task-specific additions (harness, respirator, face shield)
  • Housekeeping — clear walkways, secured materials, proper waste disposal
  • Hazard identification — any new condition reported and mitigated before work proceeds

Safety Inspection Checklist

Weekly minimum — more frequent for high-risk activities:

  • [ ] Fall protection in place for work above 6 feet
  • [ ] Excavations sloped/shored/shielded per OSHA
  • [ ] Scaffolding inspected and tagged by competent person
  • [ ] Electrical panels and temporary power GFCI protected
  • [ ] Fire extinguishers accessible and inspected
  • [ ] Crane/hoist daily inspection logged
  • [ ] Confined space permits current
  • [ ] Hot work permits current
  • [ ] First aid kit stocked and AED accessible
  • [ ] Emergency action plan posted and known

Incident Reporting

Any incident — injury, near-miss, property damage, environmental release:

  1. Administer first aid / secure scene immediately
  2. Notify superintendent and safety officer
  3. Complete incident report within 4 hours

Incident report must include:

  • Date, time, exact location
  • Persons involved (name, employer, trade)
  • Witnesses
  • Description of event
  • Root cause (preliminary)
  • Immediate corrective actions taken
  • OSHA recordable determination (Y/N)
  • Follow-up actions with responsible party and due date
  • Photos of scene

Safety Metrics

Track per project:

  • Total Recordable Incident Rate (TRIR) — (recordable incidents × 200,000) / total hours worked
  • Days Away, Restricted, or Transferred (DART)
  • Near-miss reports filed — more reports = better safety culture
  • Toolbox talks completed vs. required

Permits & Inspections

Permit Tracking

Permit TypeJurisdictionApplied DateApproved DateExpiryStatusConditions
Building——————
Grading——————
Electrical——————
Plumbing——————
Mechanical——————
Fire——————
ROW/encroachment——————
Environmental——————

Inspection Schedule

Track every required inspection:

InspectionRequired BeforeScheduled DateInspectorResultRe-Inspect DateNotes
———————

Result values: PASS · CONDITIONAL · FAIL · CANCELLED

Rules:

  • Schedule inspections minimum 48 hours in advance per jurisdiction requirements
  • Never cover work that requires inspection before the inspection passes
  • If an inspection fails, document deficiencies, assign corrective action, and reschedule immediately
  • Maintain a running inspection log for final closeout documentation

RFI (Request for Information)

RFI Lifecycle

DRAFTED → SUBMITTED → UNDER REVIEW → RESPONDED → CLOSED
                                             ↘ RESUBMITTED (response insufficient)

RFI Log

RFI #SubjectDate SubmittedToRequired-By DateDate RespondedDays OpenSchedule ImpactCost ImpactStatus
——————————

RFI Best Practices

  • Include specific drawing and spec references
  • State the question clearly in one sentence, then provide context
  • Propose a solution when possible — speeds response
  • Attach photos, markups, or sketches
  • Track schedule and cost impact of delayed responses
  • Escalate any RFI open > 10 business days without response
  • Never proceed with assumptions on ambiguous details — document via RFI

Punch List Management

Punch List Workflow

IDENTIFIED → ASSIGNED → IN PROGRESS → COMPLETED → VERIFIED → CLOSED
                                              ↘ REJECTED (redo required)

Punch List Item Record

  • Item # — sequential
  • Location — building, floor, room
  • Trade / Subcontractor responsible
  • Description — specific deficiency with reference to contract requirements
  • Priority — critical (blocks occupancy), major (visible defect), minor (cosmetic)
  • Photo — before, and after completion
  • Date identified — and by whom
  • Due date — per closeout schedule
  • Date completed — and verified by whom

Punch List Rules

  • Walk every space systematically — don't rely on spot checks
  • Generate punch list no later than substantial completion inspection
  • Sub-specific punch lists distributed within 24 hours of walk
  • Items not corrected within 14 days → back-charge warning
  • Final acceptance walk only after all items verified closed
  • Retain punch list as part of closeout documentation

Equipment Scheduling & Maintenance

Equipment Registry

Per piece of equipment (owned or rented):

  • Equipment ID / description — e.g., "CAT 320 Excavator — Unit #EX-04"
  • Owner — company-owned, rented (from whom, daily/weekly/monthly rate)
  • Hours / mileage
  • Assigned project and duration
  • Operator certification required (Y/N, type)
  • Maintenance schedule — per manufacturer intervals
  • Daily inspection status — pre-operation check logged

Equipment Schedule

EquipmentProjectMobilize DateDemobilize DateRateUtilization
——————

Track utilization: hours_used / hours_available. Below 60% → review whether equipment is needed on site. Rented equipment idle > 3 days → consider off-renting.

Maintenance / Inspection

  • Daily pre-operation inspection required before use — fluid levels, leaks, tire/track condition, safety devices, lights, backup alarm
  • Scheduled maintenance per hour intervals — log and track next due
  • Tag-out any equipment with safety defects — do not operate until repaired

Quality Control

QC Checklist by Phase

Foundation:

  • [ ] Excavation dimensions per plan
  • [ ] Bearing capacity verified (soils report / proof roll)
  • [ ] Reinforcement placed per structural drawings
  • [ ] Formwork plumb, level, braced
  • [ ] Concrete mix design approved
  • [ ] Concrete placed, vibrated, finished per spec
  • [ ] Concrete test cylinders taken
  • [ ] Curing method applied per spec

Structure:

  • [ ] Steel/connections per erection drawings
  • [ ] Bolt torque verified and documented
  • [ ] Concrete placement and testing per spec
  • [ ] Embed plates and anchor bolts surveyed
  • [ ] Tolerance checks (plumb, level, alignment)

Envelope:

  • [ ] Weather barrier installed per manufacturer requirements
  • [ ] Window/door flashing sequence correct
  • [ ] Sealant joints per spec (backer rod, depth/width ratio)
  • [ ] Roofing system per approved submittal
  • [ ] Water testing performed where specified

MEP Rough-In:

  • [ ] Routing per coordinated MEP drawings / BIM
  • [ ] Hangers and supports per code and spec
  • [ ] Fire-stopping at penetrations
  • [ ] Pressure testing (plumbing, fire protection, gas)
  • [ ] Insulation per spec

Finishes:

  • [ ] Substrate prep verified before finish application
  • [ ] Color and material match approved samples
  • [ ] Installation per manufacturer requirements
  • [ ] Protection of finished surfaces from other trades

Non-Conformance Report (NCR)

When work does not meet contract requirements:

  1. Stop work on the affected item
  2. Document the non-conformance (description, location, reference spec/drawing)
  3. Photograph the condition
  4. Issue NCR to responsible party with required corrective action
  5. Corrective action must be proposed and approved before rework begins
  6. Verify corrective work, close NCR with sign-off

Weather Impact Assessment

Decision Matrix

ConditionImpact LevelAction
Rain — light (<0.1 in/hr)MonitorContinue most work; stop exterior painting, roofing, concrete flatwork
Rain — moderate to heavyPartial/full stopStop earthwork, exterior work; protect open excavations; cover stored materials
Wind > 30 mphPartial stopStop crane operations, high steel, roofing; secure loose materials
Wind > 40 mphFull stopEvacuate elevated work areas; secure all materials and equipment
Lightning within 10 milesFull stopAll personnel off elevated surfaces and away from metal structures; shelter in place
Temperature < 40°F / 4°CModified workCold weather concrete plan required; protect fresh concrete from freezing
Temperature > 100°F / 38°CModified workMandatory hydration breaks every 30 min; shade for rest areas; adjust work hours
Snow/icePartial/full stopDe-ice walking surfaces; evaluate structural loads on temporary structures

Weather Delay Documentation

For each weather delay:

  • Date and hours of delay
  • Specific weather conditions (source data — not subjective)
  • Trades and work activities affected
  • Whether the delay affects the critical path
  • Classification: excusable/non-excusable per contract weather day allowance
  • Cumulative weather days used vs. contract allowance

Client / Owner Communication

Progress Reporting

Deliver to the owner on a defined cadence (typically monthly):

  • Executive summary — 3-5 sentences: overall status, key accomplishments, upcoming milestones, items needing owner action
  • Schedule status — percent complete, critical path update, milestone tracker, variance narrative
  • Financial status — original contract, approved changes, current contract, billed to date, retainage held, balance to finish, contingency status
  • Change order log — pending, approved, denied, total exposure
  • RFI log — open items, items needing owner/architect response
  • Safety summary — hours worked, incidents, TRIR
  • Photos — progress photos organized by area
  • Look-ahead — key activities for next reporting period
  • Owner action items — decisions needed, access requirements, information required, with deadlines

Communication Log

Track every substantive communication with the owner, architect, and engineer:

DateFromToMethodSubjectAction RequiredResolved
———————

Method values: EMAIL · MEETING · PHONE · LETTER · RFI · SUBMITTAL

Meeting Minutes Template

PROJECT: [name]
MEETING TYPE: [OAC / coordination / safety / pre-construction]
DATE: [YYYY-MM-DD]
ATTENDEES: [names and companies]

AGENDA ITEMS:
1. [topic] — [discussion summary] — [decision or action]
2. ...

ACTION ITEMS:
| # | Action | Responsible | Due Date | Status |
|---|--------|------------|----------|--------|
| — | — | — | — | — |

NEXT MEETING: [date and time]

PREPARED BY: [name] | DISTRIBUTED: [date]

Project Closeout

Closeout Checklist

  • [ ] Punch list 100% complete and verified
  • [ ] All inspections passed — certificate of occupancy obtained
  • [ ] As-built drawings submitted
  • [ ] O&M manuals delivered
  • [ ] Warranty letters collected from all subs and suppliers
  • [ ] Attic stock and spare parts delivered
  • [ ] Owner training on building systems completed and documented
  • [ ] Final pay applications processed (all subs)
  • [ ] Retainage release conditions met
  • [ ] Final change order executed (zero-balance CO if needed)
  • [ ] Lien waivers collected (conditional and unconditional, all tiers)
  • [ ] Consent of surety for final payment (if bonded)
  • [ ] Project documentation archived (submittals, RFIs, COs, daily reports, photos, test reports)
  • [ ] Lessons learned meeting conducted and documented
  • [ ] Warranty period start date and end date documented
  • [ ] Demobilization complete — site clean, temporary facilities removed

平台分布

OpenClaw

71.6%
按下载量换算1,021

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills