tweetsmash-api
TweetSmash API
Use this skill to work directly with the TweetSmash REST API after verifying the current docs. Read references/api-reference.md before choosing an endpoint. Read references/bookmarks-filters.md only when bookmark filtering is required.
Procedures
Step 1: Validate Credentials and Scope
- Confirm that a TweetSmash API key is available before making requests. Prefer
TWEETSMASH_API_KEYin the shell environment. - Read
references/api-reference.mdto confirm the current endpoint, required headers, rate limits, and status codes. - If the task requires bookmark filtering or pagination, read
references/bookmarks-filters.md.
Step 2: Build the Request
- Use
Authorization: Bearer $TWEETSMASH_API_KEYon every request. - Use
Content-Type: application/jsonfor all examples in this skill. Keep the base URL ashttps://api.tweetsmash.com/v1. - If the task fetches bookmarks with filters, execute
python3 scripts/build-bookmarks-url.pywith the needed flags to generate a correctly encoded URL. - If the task adds labels, start from
assets/add-labels-body.jsonand fill intweet_idsplus eitherlabel_idorlabel_name. - If the task removes labels, start from
assets/remove-labels-body.jsonand fill intweet_idspluslabel_name.
Step 3: Execute the Correct Endpoint
More from pedronauck/skills
skill-best-practices
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
240architectural-analysis
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health. Don't use for style/formatting issues, performance profiling, security audits, or feature-level code review.
200brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
175typescript-advanced
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects. Don't use for plain JavaScript, runtime validation libraries (Zod, Yup), or basic TypeScript syntax questions.
172ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
169no-workarounds
Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.
168