[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AXSZKT803DD8PQKD82P8M9":3,"skill-same:01M7AXSZKT803DD8PQKD82P8M9":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7AXSZKT803DD8PQKD82P8M9","rails-background-jobs",null,"Use when adding or reviewing background jobs in Rails. Configures Active Job workers, implements idempotency checks, sets up retry\u002Fdiscard strategies, selects Solid Queue (Rails 8+) or Sidekiq based on scale, and defines recurring jobs via recurring.yml or sidekiq-cron. Trigger words: background job, Active Job, Solid Queue, Sidekiq, idempotency, retry, discard, recurring job, queue.","Krishp091205\u002Fgemini-config","Krishp091205","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F307182548?v=4","01M7AXCYY4NQ9WQ7DCT3R5Q5S4","01M7AXCYYR7QFCQQ6BFRKD93YH",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frails-background-jobs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rails-background-jobs\nlicense: MIT\ndescription: >\n  Use when adding or reviewing background jobs in Rails. Configures Active Job\n  workers, implements idempotency checks, sets up retry\u002Fdiscard strategies,\n  selects Solid Queue (Rails 8+) or Sidekiq based on scale, and defines recurring\n  jobs via recurring.yml or sidekiq-cron. Trigger words: background job, Active Job,\n  Solid Queue, Sidekiq, idempotency, retry, discard, recurring job, queue.\n---\n\n# Rails Background Jobs\n\nUse this skill when the task is to add, configure, or review background jobs in a Rails application.\n\n**Core principle:** Design jobs for idempotency and safe retries. Prefer Active Job's unified API; choose backend based on Rails version and scale.\n\n## HARD-GATE\n\n```\nEVERY job MUST have its test written and validated BEFORE implementation.\n  1. Write the job spec (idempotency, retry, error handling)\n  2. Run the spec — verify it fails because the job does not exist yet\n  3. ONLY THEN write the job class\n\nEVERY job that performs a side effect (charge, email, API call) MUST have\nan idempotency check BEFORE the side effect.\n\nEVERY perform method should do only three things:\n  1. Load the record from the passed ID\n  2. Guard for idempotency \u002F permanent no-op conditions\n  3. Delegate the side effect or orchestration to a service object\n\nIf perform needs more than that, extract a service.\n\nAfter implementation: run full suite, confirm job appears in queue dashboard,\nverify idempotency by enqueueing twice and checking the second run is a no-op.\n```\n\n## Quick Reference\n\n| Aspect | Rule |\n|--------|------|\n| Arguments | Pass IDs, not objects. Load in `perform`. |\n| Idempotency | Check \"already done?\" before doing work |\n| Retries | `retry_on` for transient, `discard_on` for permanent errors |\n| Job size | Load, guard, delegate. No multi-step orchestration in `perform`. |\n| Backend (Rails 8) | Solid Queue (database-backed, no Redis) |\n| Backend (Rails 7) | Sidekiq + Redis for high throughput |\n| Recurring | `config\u002Frecurring.yml` (Solid Queue) or cron\u002Fsidekiq-cron |\n\n## Rails 8 vs Rails 7\n\n| Aspect | Rails 7 and earlier | Rails 8 |\n|--------|---------------------|---------|\n| Default | No default; set `queue_adapter` (often Sidekiq) | **Solid Queue** (database-backed) |\n| Dev\u002Ftest | `:async` or `:inline` | Same |\n| Recurring | External (cron, sidekiq-cron) | `config\u002Frecurring.yml` |\n| Dashboard | Third-party (Sidekiq Web) | **Mission Control Jobs** |\n\nSee [BACKENDS.md](.\u002FBACKENDS.md) for install steps, configuration, and dashboard setup for both Solid Queue and Sidekiq.\n\n## Examples\n\n**Pass IDs, not objects:**\n\n```ruby\n# Bad — object may be stale or deleted by perform time\nSomeJob.perform_later(@order)\n\n# Good — reload fresh inside perform\nSomeJob.perform_later(@order.id)\n```\n\n**Thin job with idempotency and retry:**\n\n```ruby\nclass SendInvoiceReminderJob \u003C ApplicationJob\n  queue_as :default\n  retry_on Net::OpenTimeout, wait: :polynomially_longer, attempts: 5\n  discard_on ActiveRecord::RecordNotFound\n\n  def perform(invoice_id)\n    invoice = Invoice.find(invoice_id)\n    return if invoice.reminder_sent_at?\n\n    InvoiceReminders::Send.call(invoice:)\n  end\nend\n```\n\n**Service owns the side effect and state update:**\n\n```ruby\nmodule InvoiceReminders\n  class Send\n    def self.call(invoice:)\n      InvoiceMailer.overdue(invoice).deliver_now\n      invoice.update!(reminder_sent_at: Time.current)\n    end\n  end\nend\n```\n\n**Recurring job (Solid Queue):**\n\n```yaml\n# config\u002Frecurring.yml\nproduction:\n  nightly_cleanup:\n    class: \"NightlyCleanupJob\"\n    schedule: \"0 2 * * *\"\n  hourly_sync:\n    class: \"HourlySyncJob\"\n    schedule: \"every 1 hour\"\n    queue: low\n```\n\n## Pitfalls\n\n| Problem | Correct approach |\n|---------|-----------------|\n| Passing ActiveRecord objects as arguments | Pass IDs — objects may be deleted or stale by perform time |\n| No idempotency check before side effects | Jobs run at-least-once; double-charging and double-emailing result |\n| `retry_on` without `attempts` limit | Infinite retries on persistent errors |\n| Missing `discard_on` for permanent errors | Job retries forever on `RecordNotFound` |\n| Complex business logic in `perform` | Keep `perform` thin — delegate to service objects |\n| Using `:inline` or `:async` in production | No persistence, no retry, no monitoring |\n| Recurring job defined only in code | Use `recurring.yml` or equivalent for visibility and recoverability |\n\n## Verification\n\nBefore calling the job done:\n\n1. Enqueue or perform the job twice and confirm the second run is a no-op.\n2. Confirm `retry_on` has an explicit `attempts:` limit and `discard_on` covers at least one permanent error.\n3. Confirm recurring jobs live in `config\u002Frecurring.yml` (Rails 8) or the chosen scheduler config.\n4. Confirm `perform` only loads, guards, and delegates.\n5. If the task asks for an ops artifact, record backend, retry, and idempotency decisions in `process_log.md`.\n\n## Integration\n\n| Skill | When to chain |\n|-------|---------------|\n| **rails-migration-safety** | Solid Queue uses DB tables; add migrations safely |\n| **rails-security-review** | Jobs receive serialized input; validate like any entry point |\n| **rspec-best-practices** | TDD gate: write job spec before implementation; use `perform_enqueued_jobs` |\n| **ruby-service-objects** | Keep `perform` thin; call service objects for business logic |\n\n## Assets\n\n- [assets\u002Fjob_patterns.md](assets\u002Fjob_patterns.md)\n- [assets\u002Fretry_examples.md](assets\u002Fretry_examples.md)\n","# Rails Background Jobs\n\nUse this skill when the task is to add, configure, or review background jobs in a Rails application.\n\n**Core principle:** Design jobs for idempotency and safe retries. Prefer Active Job's unified API; choose backend based on Rails version and scale.\n\n## HARD-GATE\n\n```\nEVERY job MUST have its test written and validated BEFORE implementation.\n  1. Write the job spec (idempotency, retry, error handling)\n  2. Run the spec — verify it fails because the job does not exist yet\n  3. ONLY THEN write the job class\n\nEVERY job that performs a side effect (charge, email, API call) MUST have\nan idempotency check BEFORE the side effect.\n\nEVERY perform method should do only three things:\n  1. Load the record from the passed ID\n  2. Guard for idempotency \u002F permanent no-op conditions\n  3. Delegate the side effect or orchestration to a service object\n\nIf perform needs more than that, extract a service.\n\nAfter implementation: run full suite, confirm job appears in queue dashboard,\nverify idempotency by enqueueing twice and checking the second run is a no-op.\n```\n\n## Quick Reference\n\n| Aspect | Rule |\n|--------|------|\n| Arguments | Pass IDs, not objects. Load in `perform`. |\n| Idempotency | Check \"already done?\" before doing work |\n| Retries | `retry_on` for transient, `discard_on` for permanent errors |\n| Job size | Load, guard, delegate. No multi-step orchestration in `perform`. |\n| Backend (Rails 8) | Solid Queue (database-backed, no Redis) |\n| Backend (Rails 7) | Sidekiq + Redis for high throughput |\n| Recurring | `config\u002Frecurring.yml` (Solid Queue) or cron\u002Fsidekiq-cron |\n\n## Rails 8 vs Rails 7\n\n| Aspect | Rails 7 and earlier | Rails 8 |\n|--------|---------------------|---------|\n| Default | No default; set `queue_adapter` (often Sidekiq) | **Solid Queue** (database-backed) |\n| Dev\u002Ftest | `:async` or `:inline` | Same |\n| Recurring | External (cron, sidekiq-cron) | `config\u002Frecurring.yml` |\n| Dashboard | Third-party (Sidekiq Web) | **Mission Control Jobs** |\n\nSee [BACKENDS.md](.\u002FBACKENDS.md) for install steps, configuration, and dashboard setup for both Solid Queue and Sidekiq.\n\n## Examples\n\n**Pass IDs, not objects:**\n\n```ruby\n# Bad — object may be stale or deleted by perform time\nSomeJob.perform_later(@order)\n\n# Good — reload fresh inside perform\nSomeJob.perform_later(@order.id)\n```\n\n**Thin job with idempotency and retry:**\n\n```ruby\nclass SendInvoiceReminderJob \u003C ApplicationJob\n  queue_as :default\n  retry_on Net::OpenTimeout, wait: :polynomially_longer, attempts: 5\n  discard_on ActiveRecord::RecordNotFound\n\n  def perform(invoice_id)\n    invoice = Invoice.find(invoice_id)\n    return if invoice.reminder_sent_at?\n\n    InvoiceReminders::Send.call(invoice:)\n  end\nend\n```\n\n**Service owns the side effect and state update:**\n\n```ruby\nmodule InvoiceReminders\n  class Send\n    def self.call(invoice:)\n      InvoiceMailer.overdue(invoice).deliver_now\n      invoice.update!(reminder_sent_at: Time.current)\n    end\n  end\nend\n```\n\n**Recurring job (Solid Queue):**\n\n```yaml\n# config\u002Frecurring.yml\nproduction:\n  nightly_cleanup:\n    class: \"NightlyCleanupJob\"\n    schedule: \"0 2 * * *\"\n  hourly_sync:\n    class: \"HourlySyncJob\"\n    schedule: \"every 1 hour\"\n    queue: low\n```\n\n## Pitfalls\n\n| Problem | Correct approach |\n|---------|-----------------|\n| Passing ActiveRecord objects as arguments | Pass IDs — objects may be deleted or stale by perform time |\n| No idempotency check before side effects | Jobs run at-least-once; double-charging and double-emailing result |\n| `retry_on` without `attempts` limit | Infinite retries on persistent errors |\n| Missing `discard_on` for permanent errors | Job retries forever on `RecordNotFound` |\n| Complex business logic in `perform` | Keep `perform` thin — delegate to service objects |\n| Using `:inline` or `:async` in production | No persistence, no retry, no monitoring |\n| Recurring job defined only in code | Use `recurring.yml` or equivalent for visibility and recoverability |\n\n## Verification\n\nBefore calling the job done:\n\n1. Enqueue or perform the job twice and confirm the second run is a no-op.\n2. Confirm `retry_on` has an explicit `attempts:` limit and `discard_on` covers at least one permanent error.\n3. Confirm recurring jobs live in `config\u002Frecurring.yml` (Rails 8) or the chosen scheduler config.\n4. Confirm `perform` only loads, guards, and delegates.\n5. If the task asks for an ops artifact, record backend, retry, and idempotency decisions in `process_log.md`.\n\n## Integration\n\n| Skill | When to chain |\n|-------|---------------|\n| **rails-migration-safety** | Solid Queue uses DB tables; add migrations safely |\n| **rails-security-review** | Jobs receive serialized input; validate like any entry point |\n| **rspec-best-practices** | TDD gate: write job spec before implementation; use `perform_enqueued_jobs` |\n| **ruby-service-objects** | Keep `perform` thin; call service objects for business logic |\n\n## Assets\n\n- [assets\u002Fjob_patterns.md](assets\u002Fjob_patterns.md)\n- [assets\u002Fretry_examples.md](assets\u002Fretry_examples.md)\n",{"name":5,"license":14,"description":7},"main","1f317365436456f9c1039c414a2f6426caabc74c",".agents\u002Fskills\u002Frails-background-jobs","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config","https:\u002F\u002Fgithub.com\u002FKrishp091205","2026-08-23 02:02:24",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add Krishp091205\u002Fgemini-config --skill rails-background-jobs",{"tool":35,"command":36},"bunx","bunx skills add Krishp091205\u002Fgemini-config --skill rails-background-jobs",{"tool":38,"command":39},"pnpm","pnpm dlx skills add Krishp091205\u002Fgemini-config --skill rails-background-jobs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frails-background-jobs\u002FSKILL.md",true,[43,49,53],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"assets\u002Fjob_patterns.md","ASSET","资产文件",1297,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frails-background-jobs\u002Fassets\u002Fjob_patterns.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Fretry_examples.md",617,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frails-background-jobs\u002Fassets\u002Fretry_examples.md",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"BACKENDS.md","REFERENCE","参考文档",1608,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frails-background-jobs\u002FBACKENDS.md",[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7B0GYVAXB2M99PR4Z3N1WW0","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7B0GQ2CKFX5P1DTV802XMAB","notebook-guidance","This skill guides the use of Jupyter notebooks for data analysis, exploration, and visualization, particularly with BigQuery. It outlines best practices for notebook execution and validation (supporting both cell-by-cell execution and full notebook generation depending on tool availability), library installation, and structuring notebooks for clarity. It also covers specific rules for data cleaning, plotting, and integrating with BigQuery SQL and machine learning workflows.\nRelevant when any of the following conditions are true:\n  1. The user request involves a data analysis, data exploration, data visualization, or data insights task that requires multiple steps, queries, or visualizations to answer.\n  2. The user explicitly requests a notebook (.ipynb).\n  3. You are creating, editing, or executing cells in a Jupyter notebook.\n  4. You need to query BigQuery from within a notebook. DO NOT use the Python BigQuery client library; instead, you MUST use the `%%bqsql` magics explained in this skill.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fnotebook-guidance\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7B0GJ1K1JE2K593JZT4CAY9","ml-best-practices","CRITICAL RULE: You MUST use this skill whenever the task involves any machine learning tasks or data analysis.\nUse this skill if the user's prompt or requirements mention any of the following:\n  * Clustering\n  * Classification\n  * Regression\n  * Time series forecasting\n  * Statistical testing\n  * Model comparison\n  * ML\n  * Data analysis\n\nSQL\u002FBigQuery ML HANDOFF: If the user requires a SQL solution, use this skill to dictate the ANALYSIS STEPS (e.g., markdown analysis cells, visualization logic), but defer to `bigquery` for all SQL syntax.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fml-best-practices\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7B0GD7FSN72WCSZ16WEDH42","managing-python-dependencies","Ensures proper Python dependency management, avoiding global `pip install` and\nadhering to project-specific tooling.\n\nUse this skill if any of the following are true:\n  1. Attempting to run `pip install {package_name}`.\n  2. Python packages or dependencies need to be added or modified.\n  3. Initiating a new Python project.\n  4. Creating a new notebook, even if just using BigQuery cells.\n  5. Generating Python code that includes `import` statements for third-party libraries.\n  6. Before executing Python scripts via the terminal to ensure the correct virtual environment is active.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fmanaging-python-dependencies\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7B0G6CC6JP6QTQGPSTBMJTX","google-cloud-storage-basics","Stores, retrieves, and manages data as objects in Cloud Storage (Google Cloud Storage, or GCS) buckets. Use when you need to interact with Cloud Storage — create or configure buckets, upload, download, stream, or transfer data, organize objects with folders, generate signed URLs, control access (IAM, ACLs, public access prevention), set storage classes and tiering (Standard, Nearline, Coldline, Archive), manage cost and lifecycle, protect data (versioning, encryption\u002FCMEK, retention and Bucket Lock, object holds, soft delete), host static websites, trigger Pub\u002FSub notifications on object changes, mount buckets as a file system (gcsfuse), or optimize storage performance at any scale. Covers the gcloud storage \u002F gsutil CLI, JSON and XML APIs, client libraries, Terraform, and Cloud Storage MCP servers. Don't use for block storage (Persistent Disk), data warehousing\u002Fanalytics (BigQuery), or databases (Cloud SQL, Spanner, Bigtable, Firestore).","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-cloud-storage-basics\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7B0G2DF32KW9A77S99QBZ4Q","gcs-security-assessment","Assesses security posture, evaluates risks, and checks SAIF compliance for Google Cloud Storage buckets or projects. Use when the user requests security scans, vulnerability checks, or SAIF assessments. Don't use when: The user is asking about non-GCS resources (Compute Engine, GKE, etc.), investigating a live production outage, or asking general security questions not tied to a specific project or bucket.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fgcs-security-assessment\u002FSKILL.md",[],[]]