Agent skill

Semantic Slicing

Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw.

MITAuto-check passed

Install Semantic Slicing

skills CLI

$ npx skills add vincentkoc/dotskills --skill semantic-slicing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vincentkoc/dotskills semantic-slicing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/semantic-slicing .claude/skills/semantic-slicing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "semantic-slicing" agent skill from https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing into .claude/skills/semantic-slicing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semantic-slicing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add vincentkoc/dotskills --skill semantic-slicing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vincentkoc/dotskills semantic-slicing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/semantic-slicing .agents/skills/semantic-slicing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "semantic-slicing" agent skill from https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing into .agents/skills/semantic-slicing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semantic-slicing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vincentkoc/dotskills --skill semantic-slicing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vincentkoc/dotskills semantic-slicing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/semantic-slicing .cursor/skills/semantic-slicing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "semantic-slicing" agent skill from https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing into .cursor/skills/semantic-slicing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semantic-slicing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/vincentkoc/dotskills.git --path skills/semantic-slicing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vincentkoc/dotskills --skill semantic-slicing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vincentkoc/dotskills semantic-slicing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/semantic-slicing .gemini/skills/semantic-slicing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "semantic-slicing" agent skill from https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing into .gemini/skills/semantic-slicing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semantic-slicing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install vincentkoc/dotskills semantic-slicing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add vincentkoc/dotskills --skill semantic-slicing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/semantic-slicing .github/skills/semantic-slicing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "semantic-slicing" agent skill from https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing into .github/skills/semantic-slicing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semantic-slicing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vincentkoc/dotskills --skill semantic-slicing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vincentkoc/dotskills semantic-slicing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/semantic-slicing .opencode/skills/semantic-slicing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "semantic-slicing" agent skill from https://github.com/vincentkoc/dotskills/tree/main/skills/semantic-slicing into .opencode/skills/semantic-slicing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semantic-slicing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: semantic-slicing
GitHub stars: 107
Token cost: ~2k tokens
SKILL.md length: 860 words
Files: 8 (incl. scripts, references, assets)
Skills in repo: 19
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw.

Works in 9 steps: Reuse suitable tool state. Create… → Read target repo instructions before… → Verify tool setup → …
SKILL.md covers Purpose, When to use, Workflow and Flow, plus 4 more sections
Runs JavaScript scripts from its folder

What it does

Semantic Slicing is an agent skill from vincentkoc/dotskills. Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `references/openclaw-profile.md` and `references/slicing-taxonomy.md`).

The repository describes itself as: 🐙 A curated set of Codex and OpenClaw skills for workflow automation, technical debugging, and agent-assisted development patterns. The licence is MIT.

Example prompts

“/semantic-slicing”

Requirements

Node.js

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

Reuse suitable tool state. Create task-owned temporary storage only when a tool requires files.
Read target repo instructions before scanning. For OpenClaw, read root AGENTS.md; subtree guides matter when reviewing a slice.
Verify tool setup
Run deterministic maps before AI review
Run scripts/semantic-map.mjs to merge the evidence into JSON on stdout.
When a visual board is requested, review it in product order
Choose a cost size before running AI stages
Run AI only at the chosen size
Report retained paths, run IDs, counts, cost size, exclusions, and skipped expensive stages in chat.

What it can do on your machine

Read from SKILL.md and the folder at commit b83ca13. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (JavaScript), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Semantic Slicing loads about 2k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 860 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from vincentkoc/dotskills at commit b83ca13, republished under its MIT licence (© vincentkoc). 860 words, ~1,964 tokens.

Download SKILL.mdSave it as .claude/skills/semantic-slicing/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.

name: semantic-slicing
description: Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw.
license: MIT
metadata.source: https://github.com/vincentkoc/dotskills

Semantic Slicing

Purpose

Turn a large repo into reviewable semantic slices with evidence. Use code shape, threat candidates, issue clusters, and support chatter together so review budget lands on the right parts of the system.

Default stance: map locally first, rank second, spend agent/security-review budget last.

When to use

Setting up or running openclaw/clawpatch against a target repo.
Setting up or running vercel-labs/deepsec against a target repo.
Producing a local visual map of feature slices, risky files, ownership clusters, or review targets.
Cross-checking code slices against gitcrawl issue/PR data or discrawl Discord/support data.
Planning a focused security, regression, architecture, or maintainer-review pass for a large repo.

Workflow

Reuse suitable tool state. Create task-owned temporary storage only when a tool requires files.
Read target repo instructions before scanning. For OpenClaw, read root AGENTS.md; subtree guides matter when reviewing a slice.
Verify tool setup:
- clawpatch: clone/build openclaw/clawpatch, then run clawpatch init, clawpatch map, clawpatch status.
- deepsec: clone/build vercel-labs/deepsec, scaffold a scratch workspace, then run deepsec scan.
- gitcrawl: run gitcrawl doctor --json, then pull clusters/threads for related issue evidence.
- discrawl: run discrawl doctor --json and discrawl status --json; use search/digest only when support chatter is relevant.
Run deterministic maps before AI review:
- Clawpatch feature map for entrypoints/packages/config/test slices.
- Deepsec regex scan for candidate threat surfaces.
- Optional repo git overlay for CODEOWNERS routing, tracked files, code/test/doc shape, and recent churn.
- Optional gitcrawl/discrawl lookups for historical pain around the same files, components, or symptoms.
Run scripts/semantic-map.mjs to merge the evidence into JSON on stdout.
- Select bounded fields for agent inspection. Do not save intermediate output by default.
- Use --out <path> only for a requested deliverable or required evidence. It retains HTML and JSON by default.
- Use --format html|json|both to select output. A single format writes only the exact --out path.
- Sparse mode is on by default and omits dotfile/config trees, docs, changelog files, and mobile app trees so core review stays focused.
- Use --no-sparse or --sparse false for the full repo; use --sparse-exclude <csv> and --sparse-include <csv> to tune the filter.
When a visual board is requested, review it in product order:
- review lanes first: semantic shape, ownership routing, development pressure, security pressure, issue pressure, support pressure,
- focus controls second: lens and system filters that narrow the matrix without duplicating rows,
- overall lens matrix third: the single slice-row table with comparable bars for semantic, ownership, development, security, issue, and support lenses,
- agent handoff packet fourth: compact JSON for follow-up agents,
- evidence tables last: raw-ish overlays for audit, not the primary reading path.
Choose a cost size before running AI stages:
- low: deterministic maps only; no deepsec process or real clawpatch review.
- medium: one to three explicit files/features with high-risk slugs, batch size 1, concurrency 1, and a turn cap.
- high: broader AI processing or multiple feature reviews; requires an explicit budget/time decision.
Run AI only at the chosen size:
- clawpatch review --feature <id> or a small --limit.
- deepsec process --files <csv> or tightly scoped --filter plus --only-slugs.
Report retained paths, run IDs, counts, cost size, exclusions, and skipped expensive stages in chat. Remove only task-owned disposable scratch when no longer needed or in use. Preserve named deliverables and recovery evidence.

Show full SKILL.md (326 more words)Show less

Flow

mermaid

stateDiagram-v2
    [*] --> ReadScopeAndInstructions
    ReadScopeAndInstructions --> ReuseToolState
    ReuseToolState --> CreateTemporaryState: required by selected tool
    ReuseToolState --> DeterministicMaps: existing state sufficient
    CreateTemporaryState --> DeterministicMaps
    DeterministicMaps --> MergeEvidence
    MergeEvidence --> ReviewBoard: visual board requested
    MergeEvidence --> ChooseCostSize: inspect stdout map
    ReviewBoard --> ChooseCostSize
    state ChooseCostSize <<choice>>
    ChooseCostSize --> ReportResults: low, no AI processing
    ChooseCostSize --> TargetedAIReview: medium, explicit files and bounded controls
    ChooseCostSize --> BroadAIReview: high, explicit budget and time decision
    ChooseCostSize --> ReportBlocked: required budget or tool unavailable
    TargetedAIReview --> ReportResults
    BroadAIReview --> ReportResults
    ReportResults --> [*]
    ReportBlocked --> [*]

Inputs

target_repo: local checkout path and/or GitHub owner/repo.
scratch_root: optional task-owned temporary directory for tools that require physical state.
out: optional requested deliverable or required evidence path. Omit it for stdout.
format: html, json, or both. Default: json without out, otherwise both.
clawpatch_repo: local clone of openclaw/clawpatch, optional if clawpatch is already on PATH.
deepsec_repo: local clone of vercel-labs/deepsec, optional if deepsec is already on PATH.
focus: optional path prefixes, issue numbers, slugs, components, or channels to prioritize.
sparse: optional map filter, default true; excludes dotfile/config, docs/changelog, and mobile app paths unless configured.
cost_size: low, medium, or high; default low.
budget_mode: map-only, targeted-ai, or full-ai; default follows cost_size.

Outputs

Tool setup status and blocker list.
Clawpatch feature counts and contamination checks.
Deepsec scan run ID, candidate counts, top slugs, and top files.
Optional repo overlays from --repo: CODEOWNERS routing, tracked files, code/test/doc shape, 90-day churn, and test-gap pressure.
Optional gitcrawl cluster/thread evidence and discrawl support evidence.
Machine-readable semantic map on stdout by default. Retained HTML and JSON only when requested.
Clean semantic buckets, ownership overlay, development overlay, security overlay, issue overlay, support overlay, and normalized queues.
Human review lanes, focus controls, agent handoff packet, and ranked next commands per lens with cost-size rationale.

Guardrails

Keep generated artifacts out of the target repo unless the user explicitly wants checked-in config.
Do not run full deepsec process or broad clawpatch review without an explicit high-cost decision; these can be expensive and noisy.
Treat local nested worktrees and dot-agent folders as contamination unless intentionally in scope: .claude/, .codex/, .agents/, .deepsec/, .semantic-slicing/.
If a tool maps contaminated paths, post-filter before ranking and call out the upstream limitation.
Never paste secrets from scan outputs. Scrub absolute personal paths before external PRs/comments.
For OpenClaw, use Testbox/Crabbox only when the task moves from mapping into validation.

References

Read references/workflow.md for concrete local setup and run commands.
Read references/slicing-taxonomy.md when choosing slice types or map layers.
Read references/openclaw-profile.md when the target is openclaw/openclaw.

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/semantic-slicing of vincentkoc/dotskills.

SKILL.md
agents/openai.yaml
assets/icon.jpg
references/openclaw-profile.md
references/slicing-taxonomy.md
references/workflow.md
scripts/semantic-map.mjs
scripts/semantic-map.test.mjs

Open the folder on GitHubat commit b83ca13

Compare with similar skills

Semantic Slicing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Semantic Slicing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Semantic Slicing this skillvincentkoc/dotskills	107	—	~2k	Automated safety check: Pass	MIT	yesterday
Clawpatchudecode/plate	17k	—	~3.7k	Automated safety check: Pass	Custom licence	today
Semantic Liststhedaviddias/Front-End-Checklist	74k	—	~504	Automated safety check: Pass	MIT	3 days ago
Semantic Versioningsickn33/agentic-awesome-skills	47k	1 repos	~2.6k	Automated safety check: Pass	MIT	today
Semantic Kernelgithub/awesome-copilot	40k	1 repos	~756	Automated safety check: Pass	MIT	today
Html5 Semantic Elementsthedaviddias/Front-End-Checklist	74k	—	~449	Automated safety check: Pass	MIT	3 days ago

Similar skills

Clawpatch
udecode/plate
Operate Clawpatch for semantic feature mapping, automated review, explicit finding fixes, revalidation, reports, and state recovery.
17k GitHub stars~3.7k tokensUpdated today
Auto-check passed
Semantic Lists
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic list elements.
74k GitHub stars~504 tokensUpdated 3 days ago
Frontend & DesignAuto-check passed
Semantic Versioning
sickn33/agentic-awesome-skills
Automate versioning and changelog generation using semantic versioning principles.
47k GitHub starsUsed in 1 repo~2.6k tokens
DevelopmentAuto-check passed
Semantic Kernel
github/awesome-copilot
Official
Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python.
40k GitHub starsUsed in 1 repo~756 tokens
DevelopmentAuto-check passed
Html5 Semantic Elements
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements.
74k GitHub stars~449 tokensUpdated 3 days ago
Auto-check passed
Vertical Slice
Donchitos/Claude-Code-Game-Studios
Pre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production.
26k GitHub stars~5.2k tokensUpdated yesterday
Game DevelopmentAuto-check: notes

Questions about Semantic Slicing

What does Semantic Slicing do?

Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw. Semantic Slicing is an agent skill from vincentkoc/dotskills. Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw.

How do I install Semantic Slicing in Claude Code?

Run `npx skills add vincentkoc/dotskills --skill semantic-slicing -a claude-code`. Or copy the skill folder (skills/semantic-slicing in vincentkoc/dotskills) into .claude/skills/semantic-slicing in your project. Claude Code loads it when a task matches its description.

How do I install Semantic Slicing in Codex?

Run `npx skills add vincentkoc/dotskills --skill semantic-slicing -a codex`. Or copy the skill folder (skills/semantic-slicing in vincentkoc/dotskills) into .agents/skills/semantic-slicing in your project. Codex loads it when a task matches its description.

Can I use Semantic Slicing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vincentkoc/dotskills --skill semantic-slicing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/semantic-slicing, .gemini/skills/semantic-slicing, .github/skills/semantic-slicing and .opencode/skills/semantic-slicing in your project.

What does Semantic Slicing need to run?

Going by SKILL.md and its folder, Semantic Slicing needs JavaScript for the scripts in its folder. Our summary lists: Node.js.

Does Semantic Slicing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Semantic Slicing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Semantic Slicing use?

Semantic Slicing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Semantic Slicing use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Semantic Slicing?

Skills that share tags, products or a category with Semantic Slicing: Clawpatch (udecode/plate, 17k stars), Semantic Lists (thedaviddias/Front-End-Checklist, 74k stars), Semantic Versioning (sickn33/agentic-awesome-skills, 47k stars) and Semantic Kernel (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Semantic Slicing?

vincentkoc (a GitHub user) maintains it in vincentkoc/dotskills, which has 107 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.

Source: vincentkoc/dotskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Semantic Slicing

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Semantic Slicing

Purpose

When to use

Workflow

Flow

Inputs

Outputs

Guardrails

References

Files

Compare with similar skills

Similar skills

More from vincentkoc/dotskills

Questions about Semantic Slicing