{
  "ocm": "1",
  "id": "pedrofuentes-powerchutetelegram-powerchutetelegram",
  "kind": "skill",
  "name": "PowerChuteTelegram",
  "description": "Repository Development Rules",
  "publisher": "pedrofuentes",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-agents"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Repository Development Rules"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-agents",
      "repository": "https://github.com/pedrofuentes/PowerChuteTelegram",
      "path": "AGENTS.md",
      "ref": "37ddb1cace7c76e914a33d2beefe8e651cbbef90",
      "url": "https://github.com/pedrofuentes/PowerChuteTelegram/blob/37ddb1cace7c76e914a33d2beefe8e651cbbef90/AGENTS.md",
      "key": "pedrofuentes/PowerChuteTelegram/AGENTS.md"
    }
  },
  "instructions": "# Repository Development Rules\n\n- Use a dedicated Git worktree for every feature or bug fix. Do not implement directly on `main`.\n- Use strict red-green-refactor TDD for every behavior change and bug fix.\n- Write one focused test first and run it to confirm it fails for the intended reason before changing production code.\n- Implement only enough code to make the focused test pass, then refactor with tests green.\n- Before completion, run the full suite under both Windows PowerShell 5.1 and PowerShell 7 and report the exact pass/fail counts.\n- Never place Telegram credentials in source, paramete",
  "cost": {
    "context_tokens": 165
  }
}