KalastajaM

ai-assistant-setup

Expert guide for setting up and improving a Claude personal assistant — covering CLAUDE.md, skills, memory, scheduled tasks, token efficiency, self-improving tasks, MCP servers, git integration, dev workflow, personal data projects, and LLM wikis. Use this skill whenever a user wants to: set up Claude as a personal assistant, write or improve a CLAUDE.md, create or refine a skill, set up memory or profiles, build or optimize a scheduled task, connect Claude to personal data (investments, finances, health, etc.), set up a new data project, add patterns to an existing project, configure MCP servers, integrate git, or asks anything like "how do I set up Claude to...", "help me improve my...", "create a skill for...", "set up a task that...", "Claude keeps forgetting...", or "how do I get Claude to work with my data". Trigger broadly — when in doubt, load this skill.

backlog

Portable project backlog manager. Use this skill whenever the user wants to review, prioritize, or add to the project backlog — including requests like "/backlog", "/backlog groom", "add this to the backlog", "what should we work on next", "let's review the backlog", "backlog session", or "what's in the backlog". Also triggers when the user brings a new idea or improvement suggestion and wants it tracked. The skill handles initialization automatically if no backlog files exist yet.

cowork-optimizer

Analyze and optimize a Cowork task or project to make it run faster, use fewer tokens, reduce unnecessary steps, and improve overall structure. Use this skill whenever the user shares a Cowork task or project and asks to optimize, improve, speed up, refactor, or reduce Claude usage. Also trigger when the user says things like "make this more efficient", "this task is slow", "can we trim this down", "review my task", or pastes a Cowork task/project definition and asks for feedback.

Data & Documents Listed

html-report

Generates polished, self-contained HTML reports, briefings, and dashboards from task or skill output. Trigger this skill whenever the user wants output as an HTML file or styled report — phrases like "make this an HTML report", "generate a dashboard", "style my briefing", "turn this summary into something I can open in a browser", or when a task's output format calls for status colours, summary metrics, or a shareable standalone page. Also trigger when converting an existing Markdown report or run log into HTML. Do NOT trigger for Markdown-only output, web app development, or emails.

policies-validator

Company policy guardrail for every Claude response. Use this skill ALWAYS before answering any question, drafting any output, running any task, or recommending any action that could touch company policy. Triggers include: drafting external or internal communications, handling data of any classification, making decisions about tools or vendors, summarising or forwarding content, content generation of any kind, recommending technical approaches with security implications, and any task or prompt that processes organisational data. If the user asks anything that could implicate the AI use policy, Claude guidelines, Code of Conduct, data classification, acceptable use, or related policies, this skill MUST be consulted first. Applies three enforcement tiers: hard block (T1), required check (T2), soft guidance (T3).

security-review

Run a phased security audit of Claude Code configuration and a target project. Use when the user asks to: review security, audit Claude Code setup, check for exposed credentials, set up security hooks, harden their Claude environment, scan a project for secrets, or anything like "check if my setup is secure", "audit my Claude config", "set up security hooks", "scan for credentials". Accepts an optional project path argument (e.g. `/security-review /path/to/project`) to scope project-level checks; defaults to the current working directory if omitted.

template-exporter

Use this skill whenever the user wants to create a reusable template from an existing Claude artifact or setup — including chat system prompts, Cowork tasks, Cowork projects, or skills. Trigger when the user says things like "turn this into a template", "create a template I can share", "make this reusable", "export this as a template", "I want to share this setup with someone", or "create a template for [task/project/skill/chat]". Also trigger when a conversation contains a full Cowork task, project, or skill definition and the user seems to want to preserve or share it. Always use this skill — even if the user just says "template" — when the context involves chat prompts, Cowork configurations, or skill definitions.

project-analyzer

Analyze another Claude project — Claude Code or Cowork, from a local folder or a GitHub repo — against the full Cluide guide set and produce a written improvement plan. Use whenever the user wants a whole-project health check or improvement plan for a Claude setup other than the obvious one in front of them. Trigger on phrases like "analyze my other Claude project", "review this repo's Claude setup against Cluide", "audit my whole assistant setup", "what should I improve in my Claude project", "generate an improvement plan for <project>", or "score my project against the Cluide guides". Not for optimizing a single Cowork task's efficiency — use the cowork-optimizer skill for that.