Loading...
Loading...
Found 43 Skills
Deployable Flue agent harness lane for HTTP, CI, Node, Cloudflare, and sandbox-backed agents.
Configures AWS Transit Gateway: creating a hub and attaching VPCs, segmenting traffic with route tables, centralizing egress and inspection through a hub (appliances or a Gateway Load Balancer endpoint), forcing east-west traffic between VPCs through AWS Network Firewall, connecting on-premises networks over the transit-gateway side of a Site-to-Site VPN or Direct Connect attachment (including ECMP to aggregate bandwidth across multiple VPN tunnels), peering transit gateways across Regions, migrating from a VPC peering mesh, and routing IP multicast. Applicable when connecting many VPCs through one router, isolating environments, forcing VPC-to-VPC traffic through a central Network Firewall, reaching on-premises over the hub, linking Regions, or moving off a peering mesh. Not applicable for single-VPC routing, VPC peering between two VPCs (vpcpeering skill), Direct Connect gateway or virtual interface setup (directconnect skill), or Route 53 DNS work.
Comprehensive reference for LINE Messaging API — webhook setup, message sending, Flex Message design, Rich Menu management, audience targeting, insights, coupons, and channel access tokens. This skill should be used when the user asks to "build a LINE Bot", "set up a webhook", "send a push message", "design a Flex Message", "create a Rich Menu", "manage audience targeting", "get messaging insights", "create a coupon campaign", "debug webhook signature verification", or mentions LINE Messaging API, LINE OA chatbot, reply/push/multicast/narrowcast/broadcast, Flex Message JSON, Rich Menu, group chat bot, channel access token, or URL schemes. Always use this skill whenever the user mentions LINE bots, chatbots, LINE OA, or any messaging-related LINE integration, even if they don't explicitly say "Messaging API".
Software Mansion's react-native-moq — Media over QUIC (MoQ) live streaming for React Native: sub-second-latency video/audio playback, camera/mic/screen publishing, and realtime data tracks over a MoQ relay. MUST USE before writing, reviewing, or debugging ANY code that uses react-native-moq or react-native-moq-ui. Trigger on: 'react-native-moq', 'MoQ', 'Media over QUIC', 'moq relay', 'moq-kit', 'useSession', 'useBroadcasts', 'useVideoPlayer', 'useAudioPlayer', 'usePublisher', 'useCamera', 'useMultiCamera', 'useMicrophone', 'useScreenBroadcast', 'useDataTrack', 'useDataMessages', 'useAudioChunks', 'useAudioSource', 'useVideoSource', 'VideoView', 'PublisherView', 'VideoPlayerView', 'BroadcastPickerView', 'createSession', 'createPublisher', 'subscribeBroadcasts'.
Software Mansion's moq-kit — native Swift (iOS) and Kotlin (Android) SDKs for Media over QUIC (moq-lite) live streaming: sub-second-latency playback, camera/microphone/screen publishing, and realtime data tracks over a MoQ relay. MUST USE before writing, reviewing, or debugging ANY code that imports MoQKit (Swift) or com.swmansion.moqkit (Kotlin); for React Native apps use the react-native-moq skill instead. Trigger on: 'moq-kit', 'MoQKit', 'Media over QUIC', 'moq-lite', 'MoQ relay', 'moq-ffi', 'BroadcastSubscription', 'DataTrackEmitter', 'CameraCapture', 'MicrophoneCapture', 'MultiCameraCapture', 'ScreenCapture', 'TrackSubscription', 'AudioDataStream', 'MoQReplayKitBroadcastSampleHandler', or a Session/Player/Publisher/Catalog from moq-kit.
Implement a chosen contribution in a fork of an open-source project: verify the user's fork already exists (stop and ask the user to fork if it does not), strictly follow the upstream repository's conventions (CONTRIBUTING.md, AGENTS.md, CLAUDE.md, PR template, commit and sign-off format), work on a branch of the fork without opening any fork PR, write equivalence-first tests, run the upstream CI/CD checks locally before pushing (the fork will not run them), sign commits per the upstream DCO/CLA convention, and post the PR body — built from the upstream PR template — in a markdown pasteable format on the Multica issue. In review iterations (the PR is already open and a maintainer left review comments), address only the explicit requests on the same fork branch and post a pasteable PR comment per PR in the same fenced-markdown format; PR discussions — replies, resolutions, ambiguous asks — are left for the humans. Use whenever a Multica issue asks to "work on the contribution", "implement <candidate> in <owner/repo>", "prepare the branch for <repo>", "turn the scouted contribution into a PR-ready diff", or to "address the review comments on <PR>" — even if the issue only names the target repo and the change to make.
Scout a single open-source project for contributions likely to be merged. Investigate candidate contributions (open good-first-issue / help-wanted issues, low-risk docs / test / small-feature work, areas with a precedent of merged AI-authored PRs), prepare a high-level plan for the top candidate(s), evaluate feasibility (merge likelihood, effort, prerequisites, maintainer norms / CI expectations), and post the result as a comment on the Multica sub-issue that scopes the project. Use whenever a sub-issue asks to "investigate potential contributions" in one project, or to "scout <owner/repo> for contributions". Investigation and planning only — never fork the repo, make code changes, or open a PR.