[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M770Q7YB6Z4QACT29N9B50VB":3,"skill-same:01M770Q7YB6Z4QACT29N9B50VB":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M770Q7YB6Z4QACT29N9B50VB","logic-lens",null,"AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.","haresh-sai06\u002FSapSynk-AI","haresh-sai06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180730984?v=4","01M75NJVH4TXYCE7FW7YVMSVFF","Haresh Sainaath S","01M75NJVHTCW1Z2P6MNCYGNSTJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity__logic-lens\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: logic-lens\ndescription: \"AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: hyhmrright\u002Flogic-lens\nsource_type: community\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens\u002Fblob\u002Fmain\u002FLICENSE\"\ndate_added: \"2026-04-29\"\nauthor: hyhmrright\ntags: [code-review, logic-analysis, debugging, security-review, claude-code]\ntools: [claude, codex, cursor, gemini]\n---\n\n# Logic Lens\n\n## Overview\n\nLogic Lens is a Claude Code skill that performs deep, logic-driven code review using formal reasoning frameworks. Unlike traditional linters that check syntax and style, Logic Lens analyzes your code for logical errors, race conditions, security vulnerabilities, type mismatches, and algorithmic flaws that only appear when you reason through the code's behavior.\n\nPowered by structured AI analysis, Logic Lens applies systematic logical inspection across 9 risk categories: null\u002Fundefined handling, type safety, concurrency, resource management, security injection, boundary conditions, algorithm correctness, state management, and API contract violations.\n\n## When to Use This Skill\n\n- Use when you want a thorough logic review before merging a PR\n- Use when a bug seems hard to find and standard linters aren't helping\n- Use when reviewing security-sensitive code paths (auth, payments, file access)\n- Use when refactoring complex business logic\n- Use when onboarding to a new codebase and need to understand risk areas\n\n## How It Works\n\nLogic Lens uses Claude Code's reasoning capabilities to:\n\n1. Parse code structure and build a mental model of data flow\n2. Apply formal logic checks across 9 risk categories\n3. Trace execution paths for edge cases and boundary conditions\n4. Identify security anti-patterns (injection, privilege escalation, data leakage)\n5. Report findings with severity levels and actionable fix suggestions\n\n## Installation\n\n```bash\n# Install via Claude Code plugin marketplace\n# Search: \"logic-lens\" in Claude Code > Extensions\n\n# Or install via NPX (Antigravity)\nnpx antigravity-awesome-skills --claude\n# Then invoke: @logic-lens\n```\n\n## Examples\n\n### Example 1: Review a Single File\n\n```\n@logic-lens review src\u002Fauth\u002Flogin.ts for security issues\n```\n\n**Logic Lens output:**\n```\n[CRITICAL] SQL Injection risk at line 42: user input concatenated into query string\n[HIGH] Missing rate limiting on login attempts\n[MEDIUM] Password comparison uses == instead of timing-safe comparison\n[LOW] Error messages may leak valid usernames (user enumeration)\n```\n\n### Example 2: Full Repository Scan\n\n```\n@logic-lens scan the entire codebase and prioritize by severity\n```\n\n### Example 3: Pre-PR Review\n\n```\n@logic-lens review all files changed in this branch before I open a PR\n```\n\n## The 9 Risk Categories\n\n| Category | What It Checks |\n|----------|----------------|\n| **Null\u002FUndefined** | Missing null checks, optional chaining gaps |\n| **Type Safety** | Implicit coercions, any-typed boundaries |\n| **Concurrency** | Race conditions, shared mutable state |\n| **Resource Management** | Unclosed handles, memory leaks |\n| **Security Injection** | SQL\u002FXSS\u002FCommand injection, path traversal |\n| **Boundary Conditions** | Off-by-one errors, integer overflow |\n| **Algorithm Correctness** | Wrong complexity, incorrect assumptions |\n| **State Management** | Inconsistent state, missing rollbacks |\n| **API Contracts** | Undocumented side effects, broken interfaces |\n\n## Best Practices\n\n- Run `@logic-lens` on authentication and payment code before every release\n- Combine with `@lint-and-validate` for full coverage: style + logic\n- Review the CRITICAL and HIGH findings first; LOW findings can be deferred\n- Use `@logic-lens` on legacy code you are about to modify to understand risk surface\n\n## Benchmark Results\n\nLogic Lens was tested against real-world codebases and caught issues missed by ESLint, TypeScript strict mode, and Snyk:\n\n- **47% of critical bugs** found were invisible to linters\n- **Race conditions** detected in async code that static analysis missed\n- **Security vulnerabilities** identified before deployment in CI pipeline\n\n## Related Skills\n\n- `@lint-and-validate` — Complementary: run after logic-lens for style\u002Fsyntax\n- `@security-auditor` — Specialized security-only deep scan\n- `@debugging-strategies` — Use when logic-lens findings need tracing\n\n## Additional Resources\n\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens)\n- [Dev.to Article: Why AI Code Review Misses the Most Dangerous Bugs](https:\u002F\u002Fdev.to\u002Fhyhmrright\u002Fwhy-ai-code-review-misses-the-most-dangerous-bugs-logic-lens-fixes-that-4a8l)\n- [Claude Code Skills Documentation](https:\u002F\u002Fdocs.anthropic.com\u002Fclaude-code)\n\n## Limitations\n\nUse this skill only when the task clearly matches the scope described above (code review and logic analysis). Logic Lens provides AI-powered analysis and should be combined with human review for production-critical decisions. Do not treat the output as a substitute for environment-specific testing or security audits.\n","# Logic Lens\n\n## Overview\n\nLogic Lens is a Claude Code skill that performs deep, logic-driven code review using formal reasoning frameworks. Unlike traditional linters that check syntax and style, Logic Lens analyzes your code for logical errors, race conditions, security vulnerabilities, type mismatches, and algorithmic flaws that only appear when you reason through the code's behavior.\n\nPowered by structured AI analysis, Logic Lens applies systematic logical inspection across 9 risk categories: null\u002Fundefined handling, type safety, concurrency, resource management, security injection, boundary conditions, algorithm correctness, state management, and API contract violations.\n\n## When to Use This Skill\n\n- Use when you want a thorough logic review before merging a PR\n- Use when a bug seems hard to find and standard linters aren't helping\n- Use when reviewing security-sensitive code paths (auth, payments, file access)\n- Use when refactoring complex business logic\n- Use when onboarding to a new codebase and need to understand risk areas\n\n## How It Works\n\nLogic Lens uses Claude Code's reasoning capabilities to:\n\n1. Parse code structure and build a mental model of data flow\n2. Apply formal logic checks across 9 risk categories\n3. Trace execution paths for edge cases and boundary conditions\n4. Identify security anti-patterns (injection, privilege escalation, data leakage)\n5. Report findings with severity levels and actionable fix suggestions\n\n## Installation\n\n```bash\n# Install via Claude Code plugin marketplace\n# Search: \"logic-lens\" in Claude Code > Extensions\n\n# Or install via NPX (Antigravity)\nnpx antigravity-awesome-skills --claude\n# Then invoke: @logic-lens\n```\n\n## Examples\n\n### Example 1: Review a Single File\n\n```\n@logic-lens review src\u002Fauth\u002Flogin.ts for security issues\n```\n\n**Logic Lens output:**\n```\n[CRITICAL] SQL Injection risk at line 42: user input concatenated into query string\n[HIGH] Missing rate limiting on login attempts\n[MEDIUM] Password comparison uses == instead of timing-safe comparison\n[LOW] Error messages may leak valid usernames (user enumeration)\n```\n\n### Example 2: Full Repository Scan\n\n```\n@logic-lens scan the entire codebase and prioritize by severity\n```\n\n### Example 3: Pre-PR Review\n\n```\n@logic-lens review all files changed in this branch before I open a PR\n```\n\n## The 9 Risk Categories\n\n| Category | What It Checks |\n|----------|----------------|\n| **Null\u002FUndefined** | Missing null checks, optional chaining gaps |\n| **Type Safety** | Implicit coercions, any-typed boundaries |\n| **Concurrency** | Race conditions, shared mutable state |\n| **Resource Management** | Unclosed handles, memory leaks |\n| **Security Injection** | SQL\u002FXSS\u002FCommand injection, path traversal |\n| **Boundary Conditions** | Off-by-one errors, integer overflow |\n| **Algorithm Correctness** | Wrong complexity, incorrect assumptions |\n| **State Management** | Inconsistent state, missing rollbacks |\n| **API Contracts** | Undocumented side effects, broken interfaces |\n\n## Best Practices\n\n- Run `@logic-lens` on authentication and payment code before every release\n- Combine with `@lint-and-validate` for full coverage: style + logic\n- Review the CRITICAL and HIGH findings first; LOW findings can be deferred\n- Use `@logic-lens` on legacy code you are about to modify to understand risk surface\n\n## Benchmark Results\n\nLogic Lens was tested against real-world codebases and caught issues missed by ESLint, TypeScript strict mode, and Snyk:\n\n- **47% of critical bugs** found were invisible to linters\n- **Race conditions** detected in async code that static analysis missed\n- **Security vulnerabilities** identified before deployment in CI pipeline\n\n## Related Skills\n\n- `@lint-and-validate` — Complementary: run after logic-lens for style\u002Fsyntax\n- `@security-auditor` — Specialized security-only deep scan\n- `@debugging-strategies` — Use when logic-lens findings need tracing\n\n## Additional Resources\n\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens)\n- [Dev.to Article: Why AI Code Review Misses the Most Dangerous Bugs](https:\u002F\u002Fdev.to\u002Fhyhmrright\u002Fwhy-ai-code-review-misses-the-most-dangerous-bugs-logic-lens-fixes-that-4a8l)\n- [Claude Code Skills Documentation](https:\u002F\u002Fdocs.anthropic.com\u002Fclaude-code)\n\n## Limitations\n\nUse this skill only when the task clearly matches the scope described above (code review and logic analysis). Logic Lens provides AI-powered analysis and should be combined with human review for production-critical decisions. Do not treat the output as a substitute for environment-specific testing or security audits.\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":36,"source":37,"license":15,"category":38,"date_added":39,"description":7,"source_repo":40,"source_type":37,"license_source":41},"safe",[26,27,28,29,30],"code-review","logic-analysis","debugging","security-review","claude-code",[32,33,34,35],"claude","codex","cursor","gemini","hyhmrright","community","development","2026-04-29","hyhmrright\u002Flogic-lens","https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens\u002Fblob\u002Fmain\u002FLICENSE","main","835716bfbede9677a779d77bfd04befb81c069ac","skills\u002Fantigravity__logic-lens","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI","https:\u002F\u002Fgithub.com\u002Fharesh-sai06","https:\u002F\u002Fharesh-sainaath.live\u002F","I am a Student pursuing Artificial Intelligence and Machine Learning at Sri Krishna College of Technology,Coimbatore.","2026-06-13 22:42:28",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add haresh-sai06\u002FSapSynk-AI --skill logic-lens",{"tool":56,"command":57},"bunx","bunx skills add haresh-sai06\u002FSapSynk-AI --skill logic-lens",{"tool":59,"command":60},"pnpm","pnpm dlx skills add haresh-sai06\u002FSapSynk-AI --skill logic-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity__logic-lens\u002FSKILL.md",true,[],[65,73,80,87,94,101],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M77GQ5PRFQMV3QBDAQPCSXJB","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__youtube-full-2\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":72},"01M77GPXXAB3Y8ZNG919MD4703","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__x-twitter-growth-2\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":72},"01M77GPSS7AFYH90Y5S6XHRXZW","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__write-a-skill-2\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":72},"01M77GPKB6HJS2X5XK03649C6R","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__workflow-builder-2\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":72},"01M77GP31EFXE1KS38XBZ1J9MN","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__webinar-marketing-2\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":72},"01M77GNNA22HWXX6CEQQ3JY2YB","vpe-advisor","VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad\u002Ftribe\u002Fchapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__vpe-advisor-2\u002FSKILL.md",[],[]]