Loading...
Loading...
Found 505 Skills
Manage tasks, track progress, and log daily updates via the ai-todo CLI. Trigger scenarios: 1) EXPLICIT — user mentions tasks, todos, to-do lists, progress tracking, daily standup, sprint planning, project management, work logs, or task completion. 2) POST-ACTION (proactive) — after git commit, git push, deploy to Vercel, merge PR, release, or any significant milestone (feature implemented, bug fixed, refactor done), proactively log progress and update/complete related tasks. When git-tools or vercel:deploy skill finishes, ALWAYS trigger this skill to record what was accomplished. 3) PRE-ACTION (proactive) — when user discusses implementation plans, architecture design, feature breakdown, technical specs, RFC, sprint planning, or requirement analysis, proactively suggest creating tasks to track planned work. When brainstorming skill completes, trigger this skill to convert outcomes into trackable tasks. 4) SESSION-END — when a work session involves substantial code changes, suggest a progress summary before ending. This skill connects to ai-todo (https://ai-todo.stringzhao.life) for persistent task management across sessions.
Manage tasks using the fine CLI. Use this skill whenever the user asks to create, view, update, or work with tasks, project requirements, feature specs, or work tracking through markdown files. Also use it when the user mentions "fine" in the context of project management, or asks about task status, step progress, or wants to break work into tracked steps.
Pre-built custom directives for json-render — formatting, math, string manipulation, and i18n. Use when working with @json-render/directives, defining custom directives with defineDirective, or adding $format, $math, $concat, $count, $truncate, $pluralize, $join, or $t to specs.
Generate deterministic SVGs from structured specs with validation and rendering. Use for icons, diagrams, charts, UI mockups, and technical drawings.
Use when working on the Evaluator plugin CLI, jobs, SDK-backed specs, or plugin-owned Evaluator skills.
Use when drafting, saving, formatting, validating, or repairing LinkedIn profile and content assets in this repository, including headlines, About sections, Experience descriptions, project copy, posts, articles, and LinkedIn image specs.
Get agentic setup prompt categories from a connected Salesforce org using the Connect API via sf api request rest. Use this skill to call GET /services/data/vXX.0/agenticsetup/categories and return the list of prompt categories, optionally with their nested prompts using fetchPrompts=true. TRIGGER when: user asks to get, fetch, retrieve, list, or show agentic setup categories, prompt categories, setup copilot categories, prompt library categories, available setup prompts, Agentforce prompt library, copilot prompts, or calls the agenticsetup categories Connect REST API. DO NOT TRIGGER when: user wants to create new categories, work with non-categories endpoints, or generate OpenAPI specs.
Use to optimize a social media profile so it converts visitors into followers and followers into leads — bio, handle, name/headline field, profile picture, banner/header, link-in-bio, CTA, pinned posts, and highlights. Run when the user says "optimize my profile/bio," "write my bio," "my Instagram/LinkedIn/TikTok bio," "profile," "link in bio," "my profile isn't converting," asks about creator mode or a professional/business account, or wants their account to convert better. Reads brand-profile, voice, audience, and social-strategy first. Treats the profile as a conversion landing page — 3-second clarity, searchable-field keywords, a who/what/why bio with one CTA, a goal-matched link, and specs for the visuals, pinned posts, and highlights. Advisory: produces a ready-to-apply per-platform spec (WoopSocial publishes posts/media; it does not edit profile fields). Judges results via native profile insights, not WoopSocial analytics.
Generate human-readable report from Intent files. Converts technical Intent specs into readable documents for stakeholders, team members, or documentation. Supports multiple output formats.
Current Claude AI and Claude Code capabilities, features, and limits. Consult before making claims about what Claude can or cannot do, what features exist, model availability, pricing, or environment differences. Use when answering "can Claude do X?", comparing Claude AI vs Code, checking current model specs, or advising on which environment suits a task.
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
Specification quality checker for spec-generator documents. Validates requirement.md, design.md, tasks.md for consistency, completeness, and quality. Detects requirement ID mismatches, missing sections, contradictions, and ambiguous expressions. English triggers: "inspect specs", "check specification quality", "validate requirements" 日本語トリガー: 「仕様書を検査」「品質チェック」「仕様を検証」「spec-inspect実行」