smykla-skalski/slug
claude/slug/skills/slug/SKILL.md
Generate a semantic slug for the current session's work and copy the `/rename type/slug` command to clipboard. Use when the user asks what to call this session, wants a branch-style name for the work done, or asks to rename the conversation.
$ install --global
skillsauthnpx skillsauth add smykla-skalski/sai slugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 14, 2026, 2:06 AM56.0s1 file scanned
SKILL.md
- name:
- slug
- description:
- Generate a semantic slug for the current session's work and copy the `/rename type/slug` command to clipboard. Use when the user asks what to call this session, wants a branch-style name for the work done, or asks to rename the conversation.
- allowed-tools:
- Bash
- user-invocable:
- true
- model:
- haiku
<!-- justify: CF-side-effect Bash is used only for pbcopy to fill clipboard at user request - intentional, not infrastructure-modifying -->
Review the entire conversation from start to finish and generate a semantic slug that captures all the meaningful work done across the session - not just the last task.
Slug format
<type>/<slug> where:
- Type:
feat,fix,chore,docs,refactor,test, orperf - Slug: 2-4 words in kebab-case, specific to the work done
Steps
- Scan the full conversation from the first message to the last - identify the core work across all tasks (what was built, fixed, changed, or researched). If the session covered multiple things, pick the dominant theme or the one that best characterizes the session as a whole.
- Pick the type that best fits. When in doubt:
featfor new things,fixfor bugs,chorefor maintenance/config,docsfor documentation,refactorfor restructuring,testfor test work. - Write a short kebab-case slug (2-4 words, no filler like "update" or "changes").
- Use the Bash tool to execute:
printf '/rename <type>/<slug>' | pbcopy- do not display this command, execute it. - Reply with exactly one line:
Copied: /rename <type>/<slug>
You MUST call the Bash tool to run the pbcopy command. Do not just display it as code.
When not to use
Skip this skill when the session has no meaningful work (e.g., just questions and answers with no code changes, config edits, or decisions made). If the session covered two completely unrelated topics with no dominant theme, pick the one with the most substantive work.
Error handling
If pbcopy is unavailable (non-macOS), fall back to xclip -selection clipboard on Linux. If neither is available, output the rename command directly in chat instead of copying.
Examples
<example> Session: added JWT-based login and refresh token handling Slug: `feat/jwt-auth` Copied: `/rename feat/jwt-auth` </example> <example> Session: debugged nil pointer panic in user service under concurrent load Slug: `fix/user-nil-pointer` Copied: `/rename fix/user-nil-pointer` </example> <example> Session: extracted shared parsing helpers out of three checker scripts into a common library Slug: `refactor/shared-checker-helpers` Copied: `/rename refactor/shared-checker-helpers` </example>Related Skills
smykla-skalski/council
development
VerifiedTrustedCommunity
Run the council workflow from a normal Copilot session only when the user explicitly asks for council review, multi-persona critique, debate, design review, code review, architecture feedback, UX review, or tradeoff analysis. Do not use it for commit, stage, merge, approval, or generic pre-commit requests. Accept the same mode syntax as the bundled council reviewers: `core|auto|core-eng|core-ux|core-mix|all|debate <problem|@file>`. During council slash-command use, the current session agent moderates reviewer agents directly. Runs broader than 6 reviewers require explicit AskUserQuestion approval before launch.
2SKILL.mdUpdated Apr 30, 2026
smykla-skalski/council
tools
VerifiedTrustedCommunity
Use when the user invokes $council, $council:council, Council review, or Council debate. Use loaded SKILL body or one direct installed `skills/council/SKILL.md` read. Direct read path must contain `/.codex/plugins/cache/sai/council/` and end `/skills/council/SKILL.md`. `cd <cwd> && sed -n ... <path>` is valid. Do not use `pwd`, `ls`, `find`, `rg`, `cat`, multiple `&&`, or `;`. Never use repo-local paths. If unavailable, stop exactly `Council not run: skill unavailable.` At most one pre-tool message, exact `Council progress:` line only. Non-final lines start `Council progress:`.
2SKILL.mdUpdated Apr 29, 2026
smykla-skalski/council
development
VerifiedTrustedCommunity
Run council reviews with sourced engineering, UX, reliability, performance, AI, and strategy persona lenses. Use when the user asks for council review, multi-persona critique, debate, design review, code review, architecture feedback, UX review, or tradeoff analysis.
2SKILL.mdUpdated Apr 29, 2026
smykla-skalski/council
development
VerifiedTrustedCommunity
Use when the user asks for council review, multi-persona critique, debate, design review, code review, architecture feedback, UX review, or tradeoff analysis. Bare invocations use `core` profile auto-detect; explicit `auto` selects the best-fit 6 personas from the sourced 27-persona engineering and UX roster. Users can still pin `core`, `core-eng`, `core-ux`, `core-mix`, `all`, or `debate`.
2SKILL.mdUpdated Apr 29, 2026