tanishqkancharla
- 31 skills
- 0 followers
- 18 hours ago last updated
- ▌ Spec Review · tanishqkancharlaReview a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.
- ▌ Glimpse Changes 2 · tanishqkancharla bundleCreate a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window. Use when the user wants a visual walkthrough of local code changes instead of a plain text diff.
- ▌ Calldiff · tanishqkancharlaDiff call stacks across git commits — like git diff, but for who-calls-whom. Shows which callees appeared, disappeared, or moved under an entrypoint across 23 languages (diff, tree, and reach). Use for agentic code review when call flow changed and line diffs bury the shape of the change.
- ▌ Opensky · tanishqkancharlaDrive native desktop apps through an async Node REPL whose opensky object matches the OpenAI Computer `@oai/sky` API, implemented on Cua Driver. Use when the user asks to operate, click, type, or automate a GUI application on macOS, Windows, or Linux.
- ▌ Prompting · tanishqkancharla bundleGuide for writing effective system prompts for LLM agents. Use when creating or editing system prompts for applications, agent configurations, or development tools.
- ▌ React Aria · tanishqkancharla bundleBuild accessible UI components with React Aria Components. Use when developers mention React Aria, react-aria-components, accessible components, or need unstyled accessible primitives. Provides documentation for building custom accessible UI with hooks and components.
- ▌ Scroll X · tanishqkancharlaExtract posts from X.com feed via Libretto workflow, then analyze for comment-worthy and generally interesting content
- ▌ Reddit Monitor · tanishqkancharlaScroll Reddit feed for commenting opportunities, generally interesting posts, and notification summaries
- ▌ Scroll Linkedin · tanishqkancharlaExtract posts from LinkedIn feed via Libretto workflow, then analyze for comment-worthy and generally interesting content
- ▌ How · tanishqkancharla bundleExplain how something works in this codebase by exploring code and producing a clear architectural explanation. Optionally critique the architecture for issues.
- ▌ Notion · tanishqkancharlaSearch, create, and manage pages in the Saffron Health Notion workspace. Use when the user asks about Notion tasks, notes, projects, or wants to interact with Notion databases.
- ▌ Get Pi Cost · tanishqkancharla bundleCheck how much has been spent on Pi sessions for a given day, broken down by model and project. Use when the user asks about Pi costs, spending, or token usage.
- ▌ Copilot Data · tanishqkancharlaLocate and inspect local data for the Copilot personal finance macOS app. Use when the user wants to find Copilot app data, inspect budgets, transactions, balances, or explain why the budget view differs from cash leaving a bank account.
- ▌ Maui · tanishqkancharlaConventions and design constraints for consuming the Maui design system. Use when building UI with Maui tokens, components, or purse-styles in an app that depends on Maui. Before designing or implementing new UI, read the closest example under src/apps/ or src/patterns/.
- ▌ Errore · tanishqkancharlaerrore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the type automatically — forget to check and your code won't compile. No wrapper types, no Result monads, just unions and instanceof. The errore npm package provides helper utilities (createTaggedError, tryAsync, matchError, findCause, partition) but the core pattern is zero-dependency. Benefits: every error is visible in the return type, callers can't forget to handle errors, flat control flow with early returns instead of nested try-catch, and errors carry typed properties with cause chains for debugging. ALWAYS read this skill when a repo uses the errore "errors as values" convention (errore.org). ALWAYS use errore for new TypeScript projects.
- ▌ Halo App · tanishqkancharla bundleDrive and test the running Halo Electron debug renderer, or inspect an extension in an isolated browser using the Halo CLI.
- ▌ Skill Creator · tanishqkancharla bundleCreate or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
- ▌ Code Walkthrough · tanishqkancharla bundleExplain implemented changes through annotated call stack diffs and prose, store the markdown in a temp directory, and serve it with tkstack.
- ▌ Halo Extension · tanishqkancharla bundleCreate, edit, run, and verify Halo workspace extensions using the bundled React, oRPC, Tandem, and connected-tool SDK.
- ▌ Testing · tanishqkancharla bundleChoose, write, and review tests that exercise real consumer behavior, prioritize successful workflows, and give each test distinct coverage. Use when adding, changing, or reviewing Vitest tests, Playwright end-to-end tests, or their harnesses.
- ▌ Database · tanishqkancharla bundleExecute SQL queries against the agent database. Use when inspecting database schema, tables, or data, verifying data after changes, or debugging database-related issues.
- ▌ Playwright · tanishqkancharlaBrowser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.
- ▌ QA Testing · tanishqkancharlaManually QA test the Electron app end-to-end using Playwright and the dev server. Use when verifying UI features, testing user flows, or performing manual QA after implementing a spec phase.
- ▌ Generate Spec · tanishqkancharlaCreate a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.
- ▌ Glimpse Changes · tanishqkancharlaCreate a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window. Use when the user wants a visual walkthrough of local code changes instead of a plain text diff.
- ▌ Push Everything · tanishqkancharlaStage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.
- ▌ Generate Spec V2 · tanishqkancharla bundleResearch and collaboratively design a significant feature, fix, or refactor, then write a phased implementation spec in specs/ and serve it with tkstack. Use when the user asks to plan, spec, scope, or phase work before implementation.
- ▌ External Electron Apps · tanishqkancharlaAutomate user-installed Electron desktop apps (Slack, Discord, VS Code, Notion, Figma, Spotify, etc.) via CDP using this repo's `.bin/playwright` CLI. Use when the task is to control a local desktop app on the user's machine, not this repo's own Electron app. Triggers: "desktop Slack app", "connect to Electron app", "remote-debugging-port", "CDP desktop app", "automate VS Code desktop app".
- ▌ Push · tanishqkancharlaCommit and push changes, creating or updating a PR as needed. Use for standard push workflow.
- ▌ Slack · tanishqkancharla bundleSlack automation CLI for AI agents. Use when: - Reading a Slack message or thread (given a URL or channel+ts) - Browsing recent channel messages / channel history - Downloading Slack attachments (snippets, images, files) to local paths - Searching Slack messages or files - Sending, editing, or deleting a message; adding/removing reactions - Listing channels/conversations; creating channels and inviting users - Fetching a Slack canvas as markdown - Looking up Slack users Triggers: "slack message", "slack thread", "slack URL", "slack link", "read slack", "reply on slack", "search slack", "channel history", "recent messages", "channel messages", "latest messages"
- ▌ Server · tanishqkancharla bundleCall RPC procedures on the local dev server. Use when inspecting server state, testing endpoints, or interacting with the app's API.