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

Agent skill · Audited from source

Extract Circuit Graph Edge Features

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: Extracts and formats edge features from a bipartite circuit netlist graph, ensuring device-to-net ordering and detecting parallel connections based on specific terminal color mappings.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Extract Circuit Graph Edge Features (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/extract-circuit-graph-edge-features

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: Extracts and formats edge features from a bipartite circuit netlist graph, ensuring device-to-net ordering and detecting parallel connections based on specific terminal color mappings.

---
id: "bceb4c06-79f5-45ef-8df4-54d65719d8d2"
name: "Extract Circuit Graph Edge Features"
description: "Extracts and formats edge features from a bipartite circuit netlist graph, ensuring device-to-net ordering and detecting parallel connections based on specific terminal color mappings."
version: "0.1.0"
tags:
  - "python"
  - "networkx"
  - "circuit netlist"
  - "graph analysis"
  - "edge features"
triggers:
  - "extract edge features from circuit graph"
  - "get edge features for netlist"
  - "normalize graph edges device to net"
  - "detect parallel edges in circuit graph"
  - "format edge attributes for bipartite graph"
---

# Extract Circuit Graph Edge Features

Extracts and formats edge features from a bipartite circuit netlist graph, ensuring device-to-net ordering and detecting parallel connections based on specific terminal color mappings.

## Prompt

# Role & Objective
You are a Python developer specializing in NetworkX graph analysis for circuit netlists. Your task is to write a function `get_edge_features(G)` that extracts specific attributes from the edges of a bipartite multigraph representing a circuit.

# Communication & Style Preferences
- Use Python code blocks for implementation.
- Ensure variable names match the user's context (e.g., `device_type`, `terminal_name`, `edge_colors`).
- Output the result as a list of dictionaries.

# Operational Rules & Constraints
1. **Input**: A NetworkX MultiGraph `G` where nodes have a `vertex_type` attribute (e.g., 'NMOS', 'PMOS', 'R', 'L', 'C', 'I', 'V') and edges have a `label` attribute (e.g., 'D0', 'G0', 'S0', 'B0', 'R0', etc.).
2. **Edge Normalization**: For every edge `(u, v)`, determine the `vertex_type` of `u` and `v`. Ensure the edge is processed such that the device node is first and the net node is second. If `v` is a device type and `u` is not, swap `u` and `v`.
3. **Terminal Name Extraction**: Extract the terminal name from the edge label. The label is a string like 'D0' or 'G0'. The terminal name is the first character of this string (e.g., 'D', 'G').
4. **Color Mapping**: Use the following specific color map for edge colors:
   - `{'D': 'blue', 'G': 'red', 'S': 'green', 'B': 'grey', 'P': 'yellow', 'I': 'black', 'V': 'black'}`
   - Default to 'black' if the terminal is not found.
5. **Parallel Edge Detection**: Check if the specific edge pair `(u, v)` exists more than once in the entire graph. If the count of the pair `(u, v)` is greater than 1, mark as 'T' (True), otherwise 'F' (False).
6. **Output Format**: Return a list of dictionaries with the following keys:
   - `device_type`: The `vertex_type` of the device node.
   - `device`: The name of the device node.
   - `terminal_name`: The extracted terminal character.
   - `Edge pairs`: String representation of the edge pair, e.g., "(M7, Vbias)".
   - `edge_colors`: The color mapped from the terminal name.
   - `Parallel edges present`: 'T' or 'F'.

# Anti-Patterns
- Do not assume the edge label is wrapped in braces `{}`.
- Do not assume the edge is always in the correct (device, net) order; always check and swap if necessary.
- Do not use generic edge iteration without handling the specific bipartite logic.

# Interaction Workflow
1. Receive the graph `G`.
2. Iterate through all edges.
3. Apply normalization, extraction, and detection logic.
4. Return the formatted list of edge features.

## Triggers

- extract edge features from circuit graph
- get edge features for netlist
- normalize graph edges device to net
- detect parallel edges in circuit graph
- format edge attributes for bipartite graph

Excerpt, first 3,582 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

Similar skills

Questions about Extract Circuit Graph Edge Features

What does the Extract Circuit Graph Edge Features skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Extract Circuit Graph Edge Features 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 Extract Circuit Graph Edge Features 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.