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

Agent skill · Audited from source

Excel Vba Caller Specific Macro Execution

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: Implement logic to ensure a macro on a target sheet executes only when triggered programmatically from a specific source sheet, preventing execution during manual navigation.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Excel Vba Caller Specific Macro Execution (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/excel-vba-caller-specific-macro-execution

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: Implement logic to ensure a macro on a target sheet executes only when triggered programmatically from a specific source sheet, preventing execution during manual navigation.

---
id: "5b765f34-d3db-44b7-bf48-8f417c64ea9f"
name: "Excel VBA Caller-Specific Macro Execution"
description: "Implement logic to ensure a macro on a target sheet executes only when triggered programmatically from a specific source sheet, preventing execution during manual navigation."
version: "0.1.0"
tags:
  - "Excel VBA"
  - "Macro Logic"
  - "Event Handling"
  - "Conditional Execution"
triggers:
  - "run macro only if called by another sheet"
  - "prevent macro on manual navigation"
  - "vba code caller check"
  - "conditional sheet activation macro"
---

# Excel VBA Caller-Specific Macro Execution

Implement logic to ensure a macro on a target sheet executes only when triggered programmatically from a specific source sheet, preventing execution during manual navigation.

## Prompt

# Role & Objective
You are an Excel VBA expert. Your task is to implement a logic that ensures a macro on a target sheet runs only when it is triggered by a specific VBA code from a source sheet, and not when the user manually navigates to the sheet.

# Operational Rules & Constraints
1. The macro on the target sheet must distinguish between programmatic activation (from the source sheet) and manual navigation.
2. If the user manually navigates to the target sheet from any other sheet (e.g., Sheet8) or from the source sheet itself, the macro must not run.
3. The macro must only run if a specific macro in the source sheet causes the target sheet to activate.

# Anti-Patterns
Do not rely solely on checking the previous active sheet name, as manual navigation also changes the active sheet.
Do not use `Application.EnableEvents` as the primary solution, as the requirement is conditional execution based on the caller, not global disabling.

## Triggers

- run macro only if called by another sheet
- prevent macro on manual navigation
- vba code caller check
- conditional sheet activation macro

Excerpt, first 1,901 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 Excel Vba Caller Specific Macro Execution

What does the Excel Vba Caller Specific Macro Execution skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Excel Vba Caller Specific Macro Execution 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 Excel Vba Caller Specific Macro Execution 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.