Topic: llm-agent
40 skills in this topic.
-
autogrind
Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'.
ttttonyhe/autogrind 6
-
autogrind
Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'.
ttttonyhe/autogrind 6
-
paper-analyze
Deep analysis of a single paper with figure extraction from arXiv source
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
auto-experiment
Launch an autonomous THINK→EXECUTE→REFLECT experiment loop on a GPU project
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
obsidian-sync
Refresh Obsidian dashboard and daily notes from current experiment state
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
daily-papers
Daily arXiv paper recommendations with automatic deduplication
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
experiment-status
Check status of running autonomous experiment loops
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
progress-report
Generate structured research progress reports
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
conf-search
Search papers from top AI/ML conferences
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
gpu-monitor
Check GPU status, running experiments, and available resources
Xiangyue-Zhang/auto-deep-researcher-24x7 302
-
skill_search
lsdefine/GenericAgent 896
-
api-workers
Cloudflare Workers deployment using `createWorkerHandler` from `@cyanheads/mcp-ts-core/worker`. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
cyanheads/mcp-ts-core 131
-
release
Verify release readiness and publish. The git wrapup protocol handles version bumps, changelog, README, commits, and tagging during the coding session. This skill verifies nothing was missed, runs final checks, and presents the irreversible publish commands.
cyanheads/mcp-ts-core 131
-
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
cyanheads/mcp-ts-core 131
-
devcheck
Lint, format, typecheck, and verify the project is clean. Use after making changes, before committing, or when the user asks to verify quality.
cyanheads/mcp-ts-core 131
-
setup
Post-init orientation for an MCP server built on @cyanheads/mcp-ts-core. Use after running `@cyanheads/mcp-ts-core init` to understand the project structure, conventions, and skill sync model. Also use when onboarding to an existing project for the first time.
cyanheads/mcp-ts-core 131
-
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
cyanheads/mcp-ts-core 131
-
api-utils
API reference for all utilities exported from `@cyanheads/mcp-ts-core/utils`. Use when looking up utility method signatures, options, peer dependencies, or usage patterns.
cyanheads/mcp-ts-core 131
-
api-config
Reference for core and server configuration in `@cyanheads/mcp-ts-core`. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.
cyanheads/mcp-ts-core 131
-
api-auth
Authentication, authorization, and multi-tenancy patterns for `@cyanheads/mcp-ts-core`. Use when implementing auth scopes on tools/resources, configuring auth modes (none/jwt/oauth), working with JWT/OAuth env vars, or understanding how tenantId flows through ctx.state.
cyanheads/mcp-ts-core 131
-
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
cyanheads/mcp-ts-core 131
-
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
cyanheads/mcp-ts-core 131
-
add-export
Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).
cyanheads/mcp-ts-core 131
-
add-app-tool
Scaffold an MCP App tool + UI resource pair. Use when the user asks to add a tool with interactive UI, create an MCP App, or build a visual/interactive tool.
cyanheads/mcp-ts-core 131