[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A75ENDTSFBYZP00DZMEJB2":3,"skill-same:01M7A75ENDTSFBYZP00DZMEJB2":65},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7A75ENDTSFBYZP00DZMEJB2","git-expert",null,"Mastery of Git protocol: internal objects (blob, tree, commit, tag), content-addressable filesystem, safe history rewriting (interactive rebase, filter-repo), reflog for recovery, local and server-side hooks, guardrails against force-pushes, secret leak detection, signed commits (GPG\u002FSSH), conventional commits, and branching strategies (trunk-based, GitHub Flow). Use when writing conventional commit messages, creating feature branches, handling merge conflicts, setting up git hooks, configuring commit signing, or enforcing push policies. Trigger: Git protocol, git merge, git rebase, git cherry-pick, git stash, git branch, git checkout, git diff, git log, conventional commits, signed commits. Do NOT trigger for: GitHub UI navigation or repository administration without Git command usage.","ronsilver\u002Fagent-covenant","ronsilver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F46677526?v=4","01M7A719H1DVMZSKNAESAC82DA","Jorge Maturana","01M7A719J5GP33TM303CB8NN00",1,"MIT","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fgit-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-expert\ndescription: \"Mastery of Git protocol: internal objects (blob, tree, commit, tag), content-addressable filesystem, safe history rewriting (interactive rebase, filter-repo), reflog for recovery, local and server-side hooks, guardrails against force-pushes, secret leak detection, signed commits (GPG\u002FSSH), conventional commits, and branching strategies (trunk-based, GitHub Flow). Use when writing conventional commit messages, creating feature branches, handling merge conflicts, setting up git hooks, configuring commit signing, or enforcing push policies. Trigger: Git protocol, git merge, git rebase, git cherry-pick, git stash, git branch, git checkout, git diff, git log, conventional commits, signed commits. Do NOT trigger for: GitHub UI navigation or repository administration without Git command usage.\"\nlicense: MIT\nmetadata:\n  author: Community\n  version: \"1.0\"\n  category: infrastructure\n  status: stable\n---\n# Git Expert\n\n**Git protocol: commits, branching, hooks, security and recovery.**\n\n## Core Stack\n\n- Protocol: Smart HTTP, SSH, Git protocol\n- Internals: Objects (blob, tree, commit, tag), packfiles, reflog\n- Branching: Trunk-Based Development (default for cloud-native projects), GitHub Flow\n- Safety: --force-with-lease, signed commits (GPG\u002FSSH), git-secrets\u002Fgitleaks\n- Conventions: Conventional Commits (default for cloud-native projects)\n\n## Conventional Commits\n\n```\ntype(scope): description\n\n[optional body]\n\n[optional footer(s)]\n```\n\n| Type | Use |\n|---|---|\n| `feat` | New feature (MINOR semver) |\n| `fix` | Bug fix (PATCH semver) |\n| `refactor` | Code restructure, no behavior change |\n| `perf` | Performance improvement |\n| `test` | Adding\u002Fupdating tests |\n| `docs` | Documentation only |\n| `chore` | Maintenance, deps, config |\n| `ci` | CI\u002FCD changes |\n| `build` | Build system changes |\n| `revert` | Revert previous commit |\n\n```\nfeat(api): add idempotency key support to resource creation\n\nImplements idempotency key validation with 24h deduplication window.\nUses Redis to store key -> response mapping with TTL.\n\nCloses #1234\n```\n\n## Signed Commits\n\n```bash\n# GPG signing\ngit config --global commit.gpgsign true\ngit config --global user.signingkey \u003CKEY_ID>\n\n# SSH signing (GitHub)\ngit config --global gpg.format ssh\ngit config --global commit.gpgsign true\ngit config --global user.signingkey ~\u002F.ssh\u002Fid_ed25519.pub\n```\n\n## Branching Strategy\n\n```bash\n# Trunk-Based Development (recommended)\nmain                     # production-ready, always deployable\n  feat\u002F\u003Cslug>            # short-lived feature branch\n  fix\u002F\u003Cslug>             # short-lived bug fix\n```\n\n### Protected branches\n\nThe following branch names are protected and MUST NEVER be used as a new\nfeature\u002Ffix branch name, nor pushed to directly:\n\n- `main`\n- `master`\n- `develop`\n- `development`\n- `staging`\n- `sandbox`\n\nAlways create a prefixed branch (`feat\u002F\u003Cslug>`, `fix\u002F\u003Cslug>`, `refactor\u002F\u003Cslug>`,\n`docs\u002F\u003Cslug>`, `test\u002F\u003Cslug>`) instead. If the chosen name collides with a\nprotected branch, pick a different prefixed name before creating it.\n\n## Safety Guardrails\n\n```bash\n# NEVER use --force on shared branches\ngit push --force-with-lease origin main           # safer force push\n\n# Recover lost commits via reflog\ngit reflog\ngit checkout HEAD@{2}                              # go back 2 operations\ngit branch recovered-branch HEAD@{2}\n\n# Undo last commit (keep changes)\ngit reset --soft HEAD~1\n```\n\n## Secrets Prevention\n\n```bash\n# Pre-commit hook to detect secrets\n# .git\u002Fhooks\u002Fpre-commit\n#!\u002Fbin\u002Fbash\nif git-secrets --scan; then\n    echo \"No secrets found\"\nelse\n    echo \"Secret detected! Commit blocked.\"\n    exit 1\nfi\n```\n\n## Conflict Resolution\n\n```bash\ngit pull --rebase origin main\n# Resolve conflicts in each file\ngit add \u003Cresolved-file>\ngit rebase --continue\ngit push --force-with-lease origin feat\u002Fmy-branch\n```\n\n## Constraints\n\n- NEVER force push to main\u002Fmaster (use --force-with-lease on feature branches only)\n- NEVER push without signed commits configured in repos\n- NEVER use git add -A \u002F git add . without reviewing changes first\n- NEVER commit secrets, .env files, or credentials (even in test fixtures)\n- ALWAYS use conventional commit format for all repos\n- ALWAYS pull --rebase before push to avoid merge bubbles\n- NEVER commit directly to main (always via PR) in protected repos\n- NEVER create a branch whose name equals a protected branch (main, master, develop, development, staging, sandbox)\n- ALWAYS ask for explicit user confirmation before `git push` (push is an ask-gated operation)\n\n## Overview\n\nMaster Git protocol: objects (blob, tree, commit, tag), safe history rewriting (interactive rebase, filter-repo), reflog for recovery, local and server-side hooks, signed commits (GPG\u002FSSH), conventional commits, secret leak detection, and branching strategies (trunk-based, GitHub Flow).\n\n## Quick Reference\n\n| Operation | Command | Safety |\n|---|---|---|\n| Force push | git push --force-with-lease | Safer than --force (checks remote) |\n| Undo last commit | git reset --soft HEAD~1 | Keeps changes staged |\n| Recover loss | git reflog + git checkout | Works for 90 days by default |\n| Signed commit | git commit -S | GPG or SSH signature |\n| Secret scan | git-secrets --scan | Pre-commit hook prevents leaks |\n\n## Workflow\n\n1. Create short-lived feature branch: `feat\u002F\u003Cslug>` or `fix\u002F\u003Cslug>`\n2. Make small commits with conventional commit format\n3. Pull --rebase before push to avoid merge bubbles\n4. Push with `--force-with-lease` if rebasing a feature branch\n5. Open PR for code review (never commit directly to main)\n6. Squash merge via PR to keep main history clean\n\n## Anti-patterns\n\nFAIL: Force pushing to shared branches without --force-with-lease\n```bash\n# BAD: overwrites remote changes without warning\ngit push --force origin main\n\n# GOOD: fails if remote has new commits\ngit push --force-with-lease origin main\n```\n\nFAIL: Committing secrets and pushing before detection\n```bash\n# BAD: secret in commit\ngit add . && git commit -m \"fix: update config\"\n# Oops — .env was included\n\n# GOOD: pre-commit hook blocks secrets\ncat > .git\u002Fhooks\u002Fpre-commit \u003C\u003C 'EOF'\n#!\u002Fbin\u002Fbash\ngit-secrets --scan || exit 1\nEOF\n```\n\nFAIL: Using `git add -A` without reviewing changes\n```bash\n# BAD: blindly stage everything\ngit add -A\n\n# GOOD: review before staging\ngit status\ngit add -p  # interactive patch staging\n```\n\n## References\n\n- Conventional Commits: https:\u002F\u002Fwww.conventionalcommits.org\u002F (last_verified: 2026-05)\n- Git documentation: https:\u002F\u002Fgit-scm.com\u002Fdoc (last_verified: 2026-05)\n- GitHub secret scanning: https:\u002F\u002Fdocs.github.com\u002Fen\u002Fcode-security\u002Fsecret-scanning (last_verified: 2026-05)\n\n- [references\u002Frecovery.md](references\u002Frecovery.md)\n- [references\u002Fworkflows.md](references\u002Fworkflows.md)\n\n## Verification Checklist\n- [ ] Conventional commit format used: `type(scope): description`\n- [ ] Signed commits configured (GPG or SSH) for cloud-native repos\n- [ ] `git push --force-with-lease` used instead of `--force` on shared branches\n- [ ] Pre-commit hook installed for secret detection (`git-secrets` or `gitleaks`)\n- [ ] No `.env`, credentials, or secrets staged before commit (reviewed with `git status` + `git diff`)\n- [ ] `git pull --rebase` used before push to avoid merge bubbles\n- [ ] Never committing directly to `main` — always via PR for protected repos\n\n## Troubleshooting\n\n| [WARN] Known issue | Likely cause | Fix |\n|---|---|---|\n| `git push --force-with-lease` rejected | Remote branch has commits you haven't pulled | Pull first: `git pull --rebase origin feat\u002Fmy-branch`, resolve conflicts, push again |\n| Secret detected after commit pushed | `.env`, `.pem`, or credentials included in commit; no pre-commit hook | Use `git filter-repo` to remove from history; rotate exposed secrets; add pre-commit hook |\n| GPG signing fails with `unusable secret key` | GPG key expired or not on this machine | Generate new key: `gpg --full-generate-key`; add to GitHub: `gpg --armor --export \u003CKEY_ID> \\| pbcopy` |\n| Merge conflict on rebase is confusing | Large PR with many commits touching same files | Use `git rebase --interactive` to squash related commits; resolve conflicts incrementally |\n| `git filter-repo` rewrites author dates even when only content changes (known limitation) | filter-repo default behavior converts author and committer timestamps to current time | Use `--refetch` or force date preservation with custom callback; document original timestamps before running |\n","# Git Expert\n\n**Git protocol: commits, branching, hooks, security and recovery.**\n\n## Core Stack\n\n- Protocol: Smart HTTP, SSH, Git protocol\n- Internals: Objects (blob, tree, commit, tag), packfiles, reflog\n- Branching: Trunk-Based Development (default for cloud-native projects), GitHub Flow\n- Safety: --force-with-lease, signed commits (GPG\u002FSSH), git-secrets\u002Fgitleaks\n- Conventions: Conventional Commits (default for cloud-native projects)\n\n## Conventional Commits\n\n```\ntype(scope): description\n\n[optional body]\n\n[optional footer(s)]\n```\n\n| Type | Use |\n|---|---|\n| `feat` | New feature (MINOR semver) |\n| `fix` | Bug fix (PATCH semver) |\n| `refactor` | Code restructure, no behavior change |\n| `perf` | Performance improvement |\n| `test` | Adding\u002Fupdating tests |\n| `docs` | Documentation only |\n| `chore` | Maintenance, deps, config |\n| `ci` | CI\u002FCD changes |\n| `build` | Build system changes |\n| `revert` | Revert previous commit |\n\n```\nfeat(api): add idempotency key support to resource creation\n\nImplements idempotency key validation with 24h deduplication window.\nUses Redis to store key -> response mapping with TTL.\n\nCloses #1234\n```\n\n## Signed Commits\n\n```bash\n# GPG signing\ngit config --global commit.gpgsign true\ngit config --global user.signingkey \u003CKEY_ID>\n\n# SSH signing (GitHub)\ngit config --global gpg.format ssh\ngit config --global commit.gpgsign true\ngit config --global user.signingkey ~\u002F.ssh\u002Fid_ed25519.pub\n```\n\n## Branching Strategy\n\n```bash\n# Trunk-Based Development (recommended)\nmain                     # production-ready, always deployable\n  feat\u002F\u003Cslug>            # short-lived feature branch\n  fix\u002F\u003Cslug>             # short-lived bug fix\n```\n\n### Protected branches\n\nThe following branch names are protected and MUST NEVER be used as a new\nfeature\u002Ffix branch name, nor pushed to directly:\n\n- `main`\n- `master`\n- `develop`\n- `development`\n- `staging`\n- `sandbox`\n\nAlways create a prefixed branch (`feat\u002F\u003Cslug>`, `fix\u002F\u003Cslug>`, `refactor\u002F\u003Cslug>`,\n`docs\u002F\u003Cslug>`, `test\u002F\u003Cslug>`) instead. If the chosen name collides with a\nprotected branch, pick a different prefixed name before creating it.\n\n## Safety Guardrails\n\n```bash\n# NEVER use --force on shared branches\ngit push --force-with-lease origin main           # safer force push\n\n# Recover lost commits via reflog\ngit reflog\ngit checkout HEAD@{2}                              # go back 2 operations\ngit branch recovered-branch HEAD@{2}\n\n# Undo last commit (keep changes)\ngit reset --soft HEAD~1\n```\n\n## Secrets Prevention\n\n```bash\n# Pre-commit hook to detect secrets\n# .git\u002Fhooks\u002Fpre-commit\n#!\u002Fbin\u002Fbash\nif git-secrets --scan; then\n    echo \"No secrets found\"\nelse\n    echo \"Secret detected! Commit blocked.\"\n    exit 1\nfi\n```\n\n## Conflict Resolution\n\n```bash\ngit pull --rebase origin main\n# Resolve conflicts in each file\ngit add \u003Cresolved-file>\ngit rebase --continue\ngit push --force-with-lease origin feat\u002Fmy-branch\n```\n\n## Constraints\n\n- NEVER force push to main\u002Fmaster (use --force-with-lease on feature branches only)\n- NEVER push without signed commits configured in repos\n- NEVER use git add -A \u002F git add . without reviewing changes first\n- NEVER commit secrets, .env files, or credentials (even in test fixtures)\n- ALWAYS use conventional commit format for all repos\n- ALWAYS pull --rebase before push to avoid merge bubbles\n- NEVER commit directly to main (always via PR) in protected repos\n- NEVER create a branch whose name equals a protected branch (main, master, develop, development, staging, sandbox)\n- ALWAYS ask for explicit user confirmation before `git push` (push is an ask-gated operation)\n\n## Overview\n\nMaster Git protocol: objects (blob, tree, commit, tag), safe history rewriting (interactive rebase, filter-repo), reflog for recovery, local and server-side hooks, signed commits (GPG\u002FSSH), conventional commits, secret leak detection, and branching strategies (trunk-based, GitHub Flow).\n\n## Quick Reference\n\n| Operation | Command | Safety |\n|---|---|---|\n| Force push | git push --force-with-lease | Safer than --force (checks remote) |\n| Undo last commit | git reset --soft HEAD~1 | Keeps changes staged |\n| Recover loss | git reflog + git checkout | Works for 90 days by default |\n| Signed commit | git commit -S | GPG or SSH signature |\n| Secret scan | git-secrets --scan | Pre-commit hook prevents leaks |\n\n## Workflow\n\n1. Create short-lived feature branch: `feat\u002F\u003Cslug>` or `fix\u002F\u003Cslug>`\n2. Make small commits with conventional commit format\n3. Pull --rebase before push to avoid merge bubbles\n4. Push with `--force-with-lease` if rebasing a feature branch\n5. Open PR for code review (never commit directly to main)\n6. Squash merge via PR to keep main history clean\n\n## Anti-patterns\n\nFAIL: Force pushing to shared branches without --force-with-lease\n```bash\n# BAD: overwrites remote changes without warning\ngit push --force origin main\n\n# GOOD: fails if remote has new commits\ngit push --force-with-lease origin main\n```\n\nFAIL: Committing secrets and pushing before detection\n```bash\n# BAD: secret in commit\ngit add . && git commit -m \"fix: update config\"\n# Oops — .env was included\n\n# GOOD: pre-commit hook blocks secrets\ncat > .git\u002Fhooks\u002Fpre-commit \u003C\u003C 'EOF'\n#!\u002Fbin\u002Fbash\ngit-secrets --scan || exit 1\nEOF\n```\n\nFAIL: Using `git add -A` without reviewing changes\n```bash\n# BAD: blindly stage everything\ngit add -A\n\n# GOOD: review before staging\ngit status\ngit add -p  # interactive patch staging\n```\n\n## References\n\n- Conventional Commits: https:\u002F\u002Fwww.conventionalcommits.org\u002F (last_verified: 2026-05)\n- Git documentation: https:\u002F\u002Fgit-scm.com\u002Fdoc (last_verified: 2026-05)\n- GitHub secret scanning: https:\u002F\u002Fdocs.github.com\u002Fen\u002Fcode-security\u002Fsecret-scanning (last_verified: 2026-05)\n\n- [references\u002Frecovery.md](references\u002Frecovery.md)\n- [references\u002Fworkflows.md](references\u002Fworkflows.md)\n\n## Verification Checklist\n- [ ] Conventional commit format used: `type(scope): description`\n- [ ] Signed commits configured (GPG or SSH) for cloud-native repos\n- [ ] `git push --force-with-lease` used instead of `--force` on shared branches\n- [ ] Pre-commit hook installed for secret detection (`git-secrets` or `gitleaks`)\n- [ ] No `.env`, credentials, or secrets staged before commit (reviewed with `git status` + `git diff`)\n- [ ] `git pull --rebase` used before push to avoid merge bubbles\n- [ ] Never committing directly to `main` — always via PR for protected repos\n\n## Troubleshooting\n\n| [WARN] Known issue | Likely cause | Fix |\n|---|---|---|\n| `git push --force-with-lease` rejected | Remote branch has commits you haven't pulled | Pull first: `git pull --rebase origin feat\u002Fmy-branch`, resolve conflicts, push again |\n| Secret detected after commit pushed | `.env`, `.pem`, or credentials included in commit; no pre-commit hook | Use `git filter-repo` to remove from history; rotate exposed secrets; add pre-commit hook |\n| GPG signing fails with `unusable secret key` | GPG key expired or not on this machine | Generate new key: `gpg --full-generate-key`; add to GitHub: `gpg --armor --export \u003CKEY_ID> \\| pbcopy` |\n| Merge conflict on rebase is confusing | Large PR with many commits touching same files | Use `git rebase --interactive` to squash related commits; resolve conflicts incrementally |\n| `git filter-repo` rewrites author dates even when only content changes (known limitation) | filter-repo default behavior converts author and committer timestamps to current time | Use `--refetch` or force date preservation with custom callback; document original timestamps before running |\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"status":26,"version":27,"category":28},"Community","stable","1.0","infrastructure","main","6692ee5cbe39d4533b824e1c55d7d4fc01c4dde7","content\u002Fskills\u002Fgit-expert",0,"https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant","https:\u002F\u002Fgithub.com\u002Fronsilver",":v","2026-08-27 05:49:26",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add ronsilver\u002Fagent-covenant --skill git-expert",{"tool":43,"command":44},"bunx","bunx skills add ronsilver\u002Fagent-covenant --skill git-expert",{"tool":46,"command":47},"pnpm","pnpm dlx skills add ronsilver\u002Fagent-covenant --skill git-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fgit-expert\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"evals\u002Fevals.json","REFERENCE","参考文档",2003,"https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fgit-expert\u002Fevals\u002Fevals.json",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Frecovery.md",561,"https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fgit-expert\u002Freferences\u002Frecovery.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fworkflows.md",570,"https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fgit-expert\u002Freferences\u002Fworkflows.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7A7HYVYNZ60GNGWAV51ZQ52","web-browsing-agent-expert","Web browsing for AI agents: driving a headless browser (Playwright, Puppeteer) from agent tooling, navigation and page-state grounding, DOM extraction and structured data capture, form interaction, session and cookie management, anti-bot mitigation awareness, and safe browsing rules (no PII exfiltration, respect robots and terms). Use when building a browsing tool or MCP server for an agent, teaching an agent to navigate and read web pages, extracting structured content from dynamic sites, or handling login walls and pagination in agent workflows. Trigger: web browsing agent, headless browser, Playwright MCP, Puppeteer, browser automation for agents, DOM extraction, page navigation, session management. Do NOT trigger for: end-to-end UI testing of an application (use playwright-expert); writing standalone scraping scripts for data pipelines (use python-expert); fetching a single public URL (use the fetch tool).","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fweb-browsing-agent-expert\u002FSKILL.md",[],[],{"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":19},"01M7A7HRC6951BAJ9NHBZA2M7Y","vector-databases","Design and operate vector databases for cloud-native AI features. Use when selecting between pgvector, Pinecone, or Weaviate for AI context layer or integration-hub; designing embedding schemas and index parameters; implementing ANN search with metadata filtering; managing embedding model versions; optimizing query latency; or debugging low retrieval quality. Pairs with rag-architecture for pipeline design and postgres-database-expert for pgvector specifics. Trigger: vector database, pgvector, Pinecone, Weaviate, embedding, ANN search, HNSW, cosine similarity. Do NOT trigger for: relational SQL optimization, standard PostgreSQL schema design, Redis caching.","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fvector-databases\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":19},"01M7A7HGHGWE7NZ5A08HQZJXDN","typescript-expert","Full-stack TypeScript stack for modern projects: frontend SSR\u002FCSR with Next.js 14 App Router and React, backend APIs with Node.js (Express\u002FFastify), state management with Zustand\u002FRedux Toolkit, unit and integration testing with Vitest\u002FJest + React Testing Library + MSW, and static analysis with ESLint\u002FPrettier\u002Ftsc. Use when building React components or hooks, implementing Next.js App Router or Server Components, writing Node.js REST API handlers, implementing middleware (auth, rate-limit, logging), managing client state (Zustand\u002FRTK), writing frontend\u002Fbackend tests, or running TypeScript linting\u002Ftype checks. Trigger: TypeScript, Next.js, React, Zustand, Node.js, Express, Fastify, MSW, Vitest. Do NOT trigger for: Python backend development, Go microservices, iOS\u002Fmobile development.","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftypescript-expert\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":19},"01M7A7H83JK9SENNYAPTTB6B4A","tool-usage","Guide correct tool selection, design, and orchestration for AI agents. Use when choosing between dedicated vs Bash tools, designing MCP tool interfaces, naming tool parameters, handling tool response limits, orchestrating parallel vs sequential calls, evaluating tool accuracy, applying ACI design principles, selecting workflow patterns, or reading\u002Ffiltering\u002Ftransforming\u002Fgenerating structured data (JSON, YAML, CSV, TOML, XML). Trigger: tool selection, MCP tool design, orchestration, ACI, parallel execution, composite tool, structured data, jq, yq, dasel, mlr, csvkit. Do NOT trigger for: writing application business logic, domain-specific development (route to domain skill), database migrations.","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftool-usage\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":19},"01M7A7GZ9A2VA9T7BJ07VV3PD5","token-efficiency","Enforce token-efficient output, compression, caching, and model routing. Use when calibrating response verbosity, applying compression strategies to logs or RAG chunks, routing tasks to the right model tier, setting thinking budgets, enforcing word limits, compressing context before reinitiation, applying KV-cache ordering, masking tool output observations, or applying clarification-first protocol before irreversible actions. Trigger: token efficiency, compression, model routing, thinking budget, KV-cache, clarification protocol. Do NOT trigger for: non-agent tooling, CI\u002FCD pipeline scripting, infrastructure provisioning.","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftoken-efficiency\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":19},"01M7A7GQFTY8GWVN4Z66Q4J52V","time-series-db","Time-series database patterns for cloud-native metrics and analytics: TimescaleDB, InfluxDB, and Amazon Timestream selection; continuous aggregates, retention policies, downsampling, and integration with Prometheus\u002FGrafana. Use when storing business metrics over time, building custom business dashboards, designing high-frequency event storage, or querying time-bucketed aggregations. Trigger: time-series, TimescaleDB, InfluxDB, Prometheus, Grafana, hypertable, continuous aggregate, retention policy. Do NOT trigger for: relational PostgreSQL schema design, NoSQL document stores, Kafka event streaming.","https:\u002F\u002Fgithub.com\u002Fronsilver\u002Fagent-covenant\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftime-series-db\u002FSKILL.md",[],[]]