Loading...
Loading...
Found 13,656 Skills
How to reach IntelliStory from any agent: the `intellistory` CLI (install, sign in, pick a project, call ANY tool with schema-checked options, upload/download media, connect Claude/Codex/Cursor/Gemini/Hermes) and the same tools over MCP. Load this first when a task mentions IntelliStory, a project code (HGRD, sq010_sh0020), shots, storyboards, looks, generation, or "put this render on the shot". Other intellistory-* skills assume this one: they name tools; this one says how to call them.
Analyze local ChatLab chat records via clb CLI. Used when users ask external Agents to review conversations, find evidence, summarize topics, compare members, or analyze specified person or group relationships based on imported ChatLab data.
Turn a recurring chore into a Superset automation — drafts the agent prompt, confirms schedule and target, creates it with the CLI, and reviews the first run together. Use when the user wants a scheduled or recurring agent, a daily/weekly job, or to automate a repeating task with Superset.
Prepare and publish Briefast's daily pre-market industry and Taiwan stock report. Use before market open when an agent must collect public news, judge short- and long-horizon stock calls, compose the exact Briefast report JSON, and POST it to the authenticated report API.
Adaptive PLAN.md executor that preserves cook-quality implementation while choosing between direct main-agent work and sub-agent delegation. Runs a phase directly through cook when delegation has no material parallelism, context, or capability benefit; otherwise dispatches disjoint assignments through encode-agent prompts, discloses agent type, model, effort, scope, and rationale before each dispatch, and acceptance-reviews every returned diff. Expects prep to have created PLAN.md + HANDOFF.md and composes with cook, encode-agent, encode-docs, and handoff. Triggers: "/cater".
Validate an ISO 17442 Legal Entity Identifier checksum and extract its issuing LOU prefix. Called as GET /v1/valid/lei, it takes lei and returns valid, lou. Observed on-chain demand: a compliance agent resolving a counterparty needs to know an LEI is well-formed before spending a lookup against a registry. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.003, paid in USDC on Base over x402.
Score text from -1 (strongly negative) to +1 (strongly positive) with a label, handling negation, intensifiers and emphasis. Called as POST /v1/text/sentiment, it takes text and returns score, label, matches, positiveTerms. A support-triage or review-monitoring agent must decide whether a message is a complaint before it routes or escalates it, and a model call for one number costs more than this and is not reproducible. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.004, paid in USDC on Base over x402.
Connect an MCP-capable coding agent to OpenChatCut and edit local video projects. Use when the user asks to install, connect, or set up OpenChatCut; inspect or edit an OpenChatCut project; work with its timeline, transcript, captions, media, generation, motion graphics, audio, color, or export tools; or recover from an OpenChatCut MCP error.
Process for generating and optimizing companion AI personas. Use this when users want to create a "sentimental, long-lasting, human-like" persona for Hermes Agent (or any AI companion role). Through a structured dialogue of "Set Tone → Name → Appearance → Personality → Background → Relationship → Speech Rhythm → Generate SOUL.md → Iterate", produce first-person persona text that can be directly pasted into Hermes' SOUL.md from a vague idea (such as "I want a JK girlfriend", "Older boyfriend", "Ice-cold royal sister"). Supports girlfriends/boyfriends and companion roles of various temperaments, and allows users to choose the output style of "send sentence by sentence" or "speak in full paragraphs". Triggered when users say "create a persona/make an AI girlfriend/boyfriend/set up a role for Hermes/optimize persona/change persona".
Converge vague requirements into a goal contract (scope / non-goals / success criteria / verification / stop conditions) that another AI can execute autonomously and be accepted. This skill only writes goal contracts, **never executes tasks for users**. Hard trigger condition: This goal is to be handed over to others for execution — subagent, Codex, another AI session, or another person. It is used to write goals, optimize goals, revise handoff prompts, or turn requests like "finish today, optimize as much as possible, help me research and execute" into task contracts that the executor won't guess randomly or overstep boundaries. Not applicable to: internal team requirement management and version breakdown (use issue-pool — it produces tasks for humans to start working on, not contracts for AI), interface design exploration (use design-exploration), PRD/acceptance criteria/test case documents (use prd-test-writer), framework planning and version roadmaps (use issue-pool), and situations where the user actually wants you to **do the task directly** — just do it directly instead of using this skill to turn the task into a document.
[user/auto] 하나의 observed 또는 measured Agent Skill anomaly를 fresh context에서 재현·격리한 뒤, 검증된 skill objective를 tk-learn으로 라우팅한다. selection, instruction, output, host, eval, stability 또는 resource incident에 사용한다. ordinary code bug, static audit, new skill creation 또는 symptom-free optimization에는 사용하지 않는다.
Create / provision / set up a NEW Digital Experience (Communities) / Experience Cloud site — employee service, IT support, help desk, HR, customer, and partner portals — via the headless-360 MCP site-creation APIs. Use whenever a user asks to create/provision/set up a portal, site, or community, e.g.: 'create an employee service portal', 'create an IT Support Portal', 'create an Agentforce Employee Center', including wiring MIAW (Messaging for In-App/Web) at create. This is the site-CREATION skill and OWNS provisioning a new Aura OR LWR Experience Builder site from scratch — trigger it even when the user says 'Experience Builder site' or 'LWR site', as long as a NEW site is wanted. It always writes a portal-creation report as its final step (never ad hoc via CLI) and never makes a legacy Tabs+Visualforce site. DO NOT TRIGGER only for modifying an EXISTING site's pages/routes/theme/branding/guest-access metadata (experience-lwr-site-generate), existing-site customization (experience-ui-bundle), CMS, Commerce.