Gws Script

A straightforward Twitter automation wrapper around inference.sh's CLI tools. Posts tweets, uploads media, handles DMs, manages follows, and does basic engagement actions like likes and retweets. The apps cover standard Twitter API functionality without the usual OAuth headache since inference.sh handles authentication. Works well for content scheduling, basic bot behaviors, or integrating Twitter into larger workflows. The media posting examples are solid for combining with AI image generation. Not groundbreaking, but removes friction if you're already using inference.sh and need reliable Twitter integration without building API clients from scratch.

This workflow pulls meeting records from Lark within a specified time range, fetches their summary documents and transcripts, then generates a structured report. It handles pagination automatically, batches API calls to stay within limits, and formats output as either daily overviews or weekly reports depending on the time span. The skill is surprisingly thorough about edge cases like meetings without summaries and proper date parsing. Most useful for managers who need weekly meeting roundups or anyone trying to track what actually got discussed across multiple sessions. The integration with Lark's document system for generating shareable reports is solid.

Combines Lark calendar events and task lists into a single standup report for any date range. Pulls your meetings, checks RSVP status, grabs incomplete tasks with due dates, then formats everything into a clean table with time conflicts highlighted and free slots calculated. Handles timezone conversion from Unix timestamps and sorts everything chronologically. Good for morning briefings or when you need to see what's actually on your plate today without switching between apps. The time conflict detection is handy since Lark doesn't always warn you about double bookings, and filtering tasks by due date keeps the output focused instead of dumping your entire backlog.

When you've got multiple independent failures across different test files or subsystems, this cuts debugging time by running separate agents in parallel instead of investigating sequentially. Each agent gets a focused scope like "fix the 3 failures in agent-tool-abort.test.ts" with all necessary context but no shared state. Works well for scenarios like timing issues in one file, API bugs in another, and race conditions in a third. The key is ensuring the problems are actually independent, otherwise agents waste time duplicating work or missing connections between failures.

This gets deep into TypeScript's type system machinery with practical patterns for building bulletproof APIs and components. You'll learn conditional types for runtime-dependent logic, mapped types for transforming interfaces, and template literals for string-based type safety. The examples show real implementations like type-safe event emitters and API clients that catch parameter mismatches at compile time. It's dense material that assumes you know basic TypeScript, but if you're building libraries or want to eliminate entire classes of runtime errors, the type gymnastics here will save you debugging time and make your code practically bulletproof.

The expo-cicd-workflows skill helps developers understand, write, and validate EAS (Expo Application Services) CI/CD workflow YAML files by providing access to current schema documentation, syntax guides, and pre-packaged job definitions. It solves the problem of keeping workflow configurations aligned with EAS's evolving specifications by fetching authoritative resources rather than relying on outdated information. The skill is designed for Expo project developers who need to configure deployment automation, build pipelines, and CI/CD triggers in their `.eas/workflows/` directory.