Borrowing it
Nothing to install: this file belongs to taurgis/sfcc-dev-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/taurgis/sfcc-dev-mcp/main/.github/skills/skill-authoring/SKILL.mdgit clone --depth 1 https://github.com/taurgis/sfcc-dev-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/taurgis/sfcc-dev-mcp/skill-authoring)<a href="https://agentmods.dev/skills/taurgis/sfcc-dev-mcp/skill-authoring"><img src="https://agentmods.dev/badge/skills/taurgis/sfcc-dev-mcp/skill-authoring.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 141 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00013 | $0.01063 |
| Opus 5 | $0.00006 | $0.00531 |
| Sonnet 5 | $0.00003 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
skill-authoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring Guide
This skill guides you through creating user-facing agent skills. For the canonical reference, see agentskills.io.
Skill Structure
A skill is a folder containing a SKILL.md file with metadata and instructions:
my-skill/
├── SKILL.md # Required: instructions + metadata
├── scripts/ # Optional: executable code
├── references/ # Optional: additional documentation
└── assets/ # Optional: templates, resources
SKILL.md Format
Required Frontmatter
---
name: skill-name
description: Brief description of what the skill does
---
- name: Unique identifier (lowercase, hyphens)
- description: One-line summary (loaded at startup for all skills - a maximum of 1000 characters)
Instructions Body
The body contains markdown instructions that tell the agent how to perform the task.
---
name: my-skill
description: Does something useful
---
# Skill Title
Brief overview of what this skill helps accomplish.
## When to Use
Describe scenarios when this skill applies.
## How to Use
Step-by-step instructions or patterns.
## Examples
Concrete examples demonstrating usage.
## Reference
- [Detailed Reference](references/REFERENCE.md) - Link to additional docs
Progressive Disclosure
Structure skills for efficient context usage:
| Layer | Token Budget | When Loaded |
|---|---|---|
| Metadata | ~100 tokens | At startup (all skills) |
| Instructions | < 5000 tokens | When skill activated |
| References | As needed | On demand |
Guidelines
- Keep SKILL.md under 500 lines - Move detailed content to references
- Front-load key information - Put most important patterns first
- Use tables for quick reference - Easy to scan
- Link to references - Don't inline everything
Optional Directories
scripts/
Executable code that agents can run:
scripts/
├── validate.sh # Validation script
├── generate.py # Code generator
└── setup.js # Setup helper
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 228 lines · 13 tokens per session scan A a5404fc905f0
skill-authoring is a skill published in the GitHub repository taurgis/sfcc-dev-mcp (27 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 1,063 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nebula-logger-instrumentation
Use this skill when the user wants to add or update Nebula Logger instrumentation in Apex, LWC, Aura, Flow, or OmniStudio. Covers logging APIs, save patterns, record association, scenarios, tags, async transaction linking, and save method selection.
nebula-logger-plugin-development
Use this skill when the user wants to build a new plugin that extends Nebula Logger - for example, custom trigger handlers on LogEntryEvente / Logc / LogEntryc, custom purge actions, or Slack-style outbound integrations. Covers the plugin framework interfaces, LoggerPluginmdt configuration, package layout, and testing…
nebula-logger-testing-your-code
Use this skill when the user wants to write Apex or LWC tests for code that calls Nebula Logger. Covers observing that the right entries were buffered, controlling logging levels inside tests, isolating tests from persisted Logc / LogEntryc / LogEntryTagc / LoggerScenarioc / LoggerTagc records, and Nebula Logger APIs…
nebula-logger-purging-and-retention
Use this skill when the user wants to configure how long Nebula Logger keeps log records before deleting or archiving them. Covers retention date semantics on Logc, the LogBatchPurger batch job, LogBatchPurgeScheduler, purge action values, and how to tune retention per user, profile, or scenario.
nebula-logger-install
Use this skill when the user wants to install and configure Nebula Logger in a Salesforce org for the first time. Covers package selection, installation paths, permissions, LoggerSettingsc hierarchy, and first-run troubleshooting.
nebula-logger-best-practices
Use this skill when the user wants to review, harden, or standardize Nebula Logger usage across a Salesforce team. Covers operational logging standards, environment-aware settings, limit-aware design, and governance guardrails.