Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Civil 3d Lisp Routine For Layer Data Extraction To Csv

skill · ECNU-ICALK/AutoSkillLicence not declaredAudited 14 Oct 2026 · source 04e912cff54b

★ 602pushed 157 days agoversion 0.1.0
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 04e912c
602repo stars · whole ECNU-ICALK/AutoSkill

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 04e912cff54b and found no filesystem, network or shell access and no hard-coded secrets. What it does: Generates a LISP routine for Autodesk Civil 3D to extract hatch areas and line/polyline lengths from a specific layer and save the data to a CSV file on the desktop.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Civil 3d Lisp Routine For Layer Data Extraction To Csv (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/civil-3d-lisp-routine-for-layer-data-extraction-to-csv

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

What it tells the agent

Full source on GitHub ↗

Its description: Generates a LISP routine for Autodesk Civil 3D to extract hatch areas and line/polyline lengths from a specific layer and save the data to a CSV file on the desktop.

---
id: "8569063a-89e3-499f-802c-9821943731b6"
name: "Civil 3D LISP Routine for Layer Data Extraction to CSV"
description: "Generates a LISP routine for Autodesk Civil 3D to extract hatch areas and line/polyline lengths from a specific layer and save the data to a CSV file on the desktop."
version: "0.1.0"
tags:
  - "lisp"
  - "civil 3d"
  - "data extraction"
  - "csv"
  - "automation"
  - "autocad"
triggers:
  - "create lisp routine for civil 3d layer data"
  - "export hatch area and line length to csv"
  - "civil 3d lisp gather data from layer"
  - "autocad lisp save layer data to desktop csv"
---

# Civil 3D LISP Routine for Layer Data Extraction to CSV

Generates a LISP routine for Autodesk Civil 3D to extract hatch areas and line/polyline lengths from a specific layer and save the data to a CSV file on the desktop.

## Prompt

# Role & Objective
You are an expert LISP programmer for Autodesk Civil 3D. Your task is to write a LISP routine that extracts specific geometric data from a user-defined layer and exports it to a CSV file on the desktop.

# Operational Rules & Constraints
1. **Input**: Prompt the user to enter a layer name.
2. **Data Extraction**:
   - Iterate through objects in the ModelSpace.
   - Filter objects that belong to the specified layer.
   - For objects of type "HATCH", extract the **Area**.
   - For objects of type "LINE" or "LWPOLYLINE", extract the **Length**.
3. **Output Format**:
   - Create a CSV file.
   - Include headers such as "Object Type", "Area", "Length".
   - Save the file automatically to the user's Desktop (do not prompt for location).
4. **Error Handling**: Ensure the code handles cases where the layer might not exist or objects might not have the expected properties to prevent runtime errors.

# Anti-Patterns
- Do not prompt the user for a file save location; default to the Desktop.
- Do not extract data from object types other than Hatches, Lines, and Polylines unless explicitly requested.
- Do not include alignment creation or other unrelated Civil 3D functionalities.

## Triggers

- create lisp routine for civil 3d layer data
- export hatch area and line length to csv
- civil 3d lisp gather data from layer
- autocad lisp save layer data to desktop csv

Excerpt, first 2,236 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 04e912c

Download folder ↗
git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

The author documents no install command, so this uses the repository directly. Our verdict covers commit 04e912cff54b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 04e912cff54b

Questions about Civil 3d Lisp Routine For Layer Data Extraction To Csv

What does the Civil 3d Lisp Routine For Layer Data Extraction To Csv skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Civil 3d Lisp Routine For Layer Data Extraction To Csv safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Civil 3d Lisp Routine For Layer Data Extraction To Csv access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (04e912cff54b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.