662건 · 관련도순
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and configure GitHub Actions. Use when building custom actions, setting up runners, implementing security practices, or publishing to the marketplace.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
E-commerce product-management desk (Busabase App-in-Skill) for catalog master data, SKUs, pricing, inventory, channel status, content assets, compliance notes, lifecycle state, and approval-gated product operations. Use when the user invokes $kelly-products or /kelly-products, asks for 电商商品管理, 商品库, SKU 管理, inventory/reorder, product status across Amazon/Shopify/TikTok Shop/eBay, channel publishing approvals, price-change review, quality holds, product lifecycle/archive decisions, or a Busabase-backed product management desk.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Repurpose source content into channel-ready drafts with a Busabase App-in-Skill review and export workflow. Use when the user asks to write content, make a content pack, turn a main blog/long article/transcript/notes into Xiaohongshu, WeChat, newsletter, LinkedIn, X/Twitter, short video scripts, SEO snippets, or a multi-platform publishing plan; also use when they ask for a content approval dashboard or App-in-Skill content workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and operate a WeChat editorial content library in Busabase. Use when a team wants reusable source material, linked article drafts, an editorial kanban board, a publishing calendar, or a source-check and review queue. Keeps source documents and article scheduling in two linked Bases; does not publish to WeChat or approve an agent's own proposals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Social media command desk (Busabase App-in-Skill) for Kelly's Twitter/X, Facebook, and Instagram accounts (extensible to LinkedIn, YouTube, Threads, TikTok, Xiaohongshu), covering cross-platform monitoring and ECHO-based publishing. Use when the user invokes $kelly-social or /kelly-social, wants cross-platform account metrics and timelines, or needs a content calendar, draft review, engagement inbox, crisis playbook, share-of-voice, or pre-publish quality gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Natural, identity-preserving portrait retouching with a local CLI and a Busabase-backed review app. Use when the user asks to 美颜, 修人像, 磨皮, 提亮肤色, portrait retouch, headshot cleanup, profile-photo polish, before/after comparison, or batch portrait enhancement. Default to local non-destructive processing, preserve facial structure and skin texture, and require explicit approval before replacing or publishing any image.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub Actions CI/CD for GNOME apps — build+test with GTK4/libadwaita on runners, Flatpak builds via flatpak-github-actions, attaching .flatpak bundles to releases, optional OCI publishing to GHCR, and headless GUI smoke tests with Xvfb/AT-SPI. Use when setting up CI, release automation, or GUI testing for a GTK app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when planning a Humans sprint — grooming the backlog into work batches and publishing the Peter-approved subset as a cloud sprint tracking issue. Runs locally with gh access to both repos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resize and convert manuscript images to KDP-compliant dimensions at 300 DPI for print-on-demand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawns and attaches sensors on a running CARLA server — cameras (rgb/depth/semantic/instance/optical-flow/normals), lidar, radar, IMU, GNSS, collision/lane-invasion/obstacle — to the ego or any actor, with a mount transform and blueprint attributes (resolution, fov, sensor_tick, lidar range/points, …). Also sets up native ROS 2 publishing (--ros to enable_for_ros, --ros-name/--ros-frame-id topic and TF naming) and prints the topics the sensor will publish. Use when the user asks to "add a camera/lidar/sensor", "put a dashcam on the ego", "attach a depth camera", "mount a sensor", or "publish a sensor to ROS". Prints the sensor id; read its data with the read-sensor skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inspects and visualises a ROS-2-enabled CARLA server from Docker containers, with no local ROS 2 install — list/echo/rate-check topics (the "are the topics actually on the wire" check), run the bundled map-and-lidar demo stack (hero vehicle with camera/lidar/GNSS/IMU on autopilot), and open RViz2 with the lane-network preset. Use when the user asks to "check the ROS topics", "echo /carla/map", "is CARLA publishing to ROS", "visualise the lidar in RViz", "open rviz", or "run the ROS 2 demo".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Queries the live CARLA world and resolves an entity description into a concrete actor id — find actors by type, role, or colour, or the single one nearest a point/actor; read the world snapshot; get static level bounding boxes by label; cast rays for semantic points; project a point to the ground; or (ros-topics) list the native ROS 2 topics each actor should be publishing and why any is silent. Identifies by stable attributes, not by any rank/order. Use when the user asks "what actors are here", "find the red prius", "the vehicle nearest the ego", "list the pedestrians", or needs a specific actor id for another skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawns vehicles on a running CARLA server and destroys them — scattered across the map's spawn points on Traffic Manager autopilot, a row queued in a single lane at a fixed spacing, or a single hero/ego vehicle (optionally named for native ROS 2 publishing with --ros-name). Covers blueprint filtering, the atomic autopilot hand-off, and cleanup. Use when the user asks to "spawn vehicles/cars/traffic", "add N cars driving around", "put cars in a lane 15 m apart", "spawn the ego/hero vehicle", or "remove the vehicles".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The shared Codex web-work inbox. Use when a coding agent needs browser work, provider account setup, OAuth or ecommerce portal work, npm publishing, or recovery of an incomplete Vault/account handoff delegated to Codex.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The CI cost rules ($100/week of real money, all CI). Use when editing .github/workflows, adding a schedule or cron, dispatching a workflow, publishing a package version, hitting a billing block, or seeing a CI SPEND OFF TRACK line, ci-breaker issue or spend alert.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare two versions of an AEM Edge Delivery Services page to identify what changed. Fetches preview vs live, or two different URLs, and produces a detailed content diff showing added, removed, and modified content, metadata, and blocks. Use when reviewing changes before publishing, auditing content modifications, or tracking content evolution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.