[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1MS3X6183XQVR0SJ3AQJB":3,"skill-same:01M7F1MS3X6183XQVR0SJ3AQJB":56},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F1MS3X6183XQVR0SJ3AQJB","python-testing-patterns",null,"Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-testing-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: python-testing-patterns\ndescription: Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.\n---\n\n# Python Testing Patterns\n\nComprehensive guide to implementing robust testing strategies in Python using pytest, fixtures, mocking, parameterization, and test-driven development practices.\n\n## When to Use This Skill\n\n- Writing unit tests for Python code\n- Setting up test suites and test infrastructure\n- Implementing test-driven development (TDD)\n- Creating integration tests for APIs and services\n- Mocking external dependencies and services\n- Testing async code and concurrent operations\n- Setting up continuous testing in CI\u002FCD\n- Implementing property-based testing\n- Testing database operations\n- Debugging failing tests\n\n## Core Concepts\n\n### 1. Test Types\n\n- **Unit Tests**: Test individual functions\u002Fclasses in isolation\n- **Integration Tests**: Test interaction between components\n- **Functional Tests**: Test complete features end-to-end\n- **Performance Tests**: Measure speed and resource usage\n\n### 2. Test Structure (AAA Pattern)\n\n- **Arrange**: Set up test data and preconditions\n- **Act**: Execute the code under test\n- **Assert**: Verify the results\n\n### 3. Test Coverage\n\n- Measure what code is exercised by tests\n- Identify untested code paths\n- Aim for meaningful coverage, not just high percentages\n\n### 4. Test Isolation\n\n- Tests should be independent\n- No shared state between tests\n- Each test should clean up after itself\n\n## Quick Start\n\n```python\n# test_example.py\ndef add(a, b):\n    return a + b\n\ndef test_add():\n    \"\"\"Basic test example.\"\"\"\n    result = add(2, 3)\n    assert result == 5\n\ndef test_add_negative():\n    \"\"\"Test with negative numbers.\"\"\"\n    assert add(-1, 1) == 0\n\n# Run with: pytest test_example.py\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Testing Best Practices\n\n### Test Organization\n\n```python\n# tests\u002F\n#   __init__.py\n#   conftest.py           # Shared fixtures\n#   test_unit\u002F            # Unit tests\n#     test_models.py\n#     test_utils.py\n#   test_integration\u002F     # Integration tests\n#     test_api.py\n#     test_database.py\n#   test_e2e\u002F            # End-to-end tests\n#     test_workflows.py\n```\n\n### Test Naming Convention\n\nA common pattern: `test_\u003Cunit>_\u003Cscenario>_\u003Cexpected_outcome>`. Adapt to your team's preferences.\n\n```python\n# Pattern: test_\u003Cunit>_\u003Cscenario>_\u003Cexpected>\ndef test_create_user_with_valid_data_returns_user():\n    ...\n\ndef test_create_user_with_duplicate_email_raises_conflict():\n    ...\n\ndef test_get_user_with_unknown_id_returns_none():\n    ...\n\n# Good test names - clear and descriptive\ndef test_user_creation_with_valid_data():\n    \"\"\"Clear name describes what is being tested.\"\"\"\n    pass\n\ndef test_login_fails_with_invalid_password():\n    \"\"\"Name describes expected behavior.\"\"\"\n    pass\n\ndef test_api_returns_404_for_missing_resource():\n    \"\"\"Specific about inputs and expected outcomes.\"\"\"\n    pass\n\n# Bad test names - avoid these\ndef test_1():  # Not descriptive\n    pass\n\ndef test_user():  # Too vague\n    pass\n\ndef test_function():  # Doesn't explain what's tested\n    pass\n```\n\n### Testing Retry Behavior\n\nVerify that retry logic works correctly using mock side effects.\n\n```python\nfrom unittest.mock import Mock\n\ndef test_retries_on_transient_error():\n    \"\"\"Test that service retries on transient failures.\"\"\"\n    client = Mock()\n    # Fail twice, then succeed\n    client.request.side_effect = [\n        ConnectionError(\"Failed\"),\n        ConnectionError(\"Failed\"),\n        {\"status\": \"ok\"},\n    ]\n\n    service = ServiceWithRetry(client, max_retries=3)\n    result = service.fetch()\n\n    assert result == {\"status\": \"ok\"}\n    assert client.request.call_count == 3\n\ndef test_gives_up_after_max_retries():\n    \"\"\"Test that service stops retrying after max attempts.\"\"\"\n    client = Mock()\n    client.request.side_effect = ConnectionError(\"Failed\")\n\n    service = ServiceWithRetry(client, max_retries=3)\n\n    with pytest.raises(ConnectionError):\n        service.fetch()\n\n    assert client.request.call_count == 3\n\ndef test_does_not_retry_on_permanent_error():\n    \"\"\"Test that permanent errors are not retried.\"\"\"\n    client = Mock()\n    client.request.side_effect = ValueError(\"Invalid input\")\n\n    service = ServiceWithRetry(client, max_retries=3)\n\n    with pytest.raises(ValueError):\n        service.fetch()\n\n    # Only called once - no retry for ValueError\n    assert client.request.call_count == 1\n```\n\n### Mocking Time with Freezegun\n\nUse freezegun to control time in tests for predictable time-dependent behavior.\n\n```python\nfrom freezegun import freeze_time\nfrom datetime import datetime, timedelta\n\n@freeze_time(\"2026-01-15 10:00:00\")\ndef test_token_expiry():\n    \"\"\"Test token expires at correct time.\"\"\"\n    token = create_token(expires_in_seconds=3600)\n    assert token.expires_at == datetime(2026, 1, 15, 11, 0, 0)\n\n@freeze_time(\"2026-01-15 10:00:00\")\ndef test_is_expired_returns_false_before_expiry():\n    \"\"\"Test token is not expired when within validity period.\"\"\"\n    token = create_token(expires_in_seconds=3600)\n    assert not token.is_expired()\n\n@freeze_time(\"2026-01-15 12:00:00\")\ndef test_is_expired_returns_true_after_expiry():\n    \"\"\"Test token is expired after validity period.\"\"\"\n    token = Token(expires_at=datetime(2026, 1, 15, 11, 30, 0))\n    assert token.is_expired()\n\ndef test_with_time_travel():\n    \"\"\"Test behavior across time using freeze_time context.\"\"\"\n    with freeze_time(\"2026-01-01\") as frozen_time:\n        item = create_item()\n        assert item.created_at == datetime(2026, 1, 1)\n\n        # Move forward in time\n        frozen_time.move_to(\"2026-01-15\")\n        assert item.age_days == 14\n```\n\n### Test Markers\n\n```python\n# test_markers.py\nimport pytest\n\n@pytest.mark.slow\ndef test_slow_operation():\n    \"\"\"Mark slow tests.\"\"\"\n    import time\n    time.sleep(2)\n\n\n@pytest.mark.integration\ndef test_database_integration():\n    \"\"\"Mark integration tests.\"\"\"\n    pass\n\n\n@pytest.mark.skip(reason=\"Feature not implemented yet\")\ndef test_future_feature():\n    \"\"\"Skip tests temporarily.\"\"\"\n    pass\n\n\n@pytest.mark.skipif(os.name == \"nt\", reason=\"Unix only test\")\ndef test_unix_specific():\n    \"\"\"Conditional skip.\"\"\"\n    pass\n\n\n@pytest.mark.xfail(reason=\"Known bug #123\")\ndef test_known_bug():\n    \"\"\"Mark expected failures.\"\"\"\n    assert False\n\n\n# Run with:\n# pytest -m slow          # Run only slow tests\n# pytest -m \"not slow\"    # Skip slow tests\n# pytest -m integration   # Run integration tests\n```\n\n### Coverage Reporting\n\n```bash\n# Install coverage\npip install pytest-cov\n\n# Run tests with coverage\npytest --cov=myapp tests\u002F\n\n# Generate HTML report\npytest --cov=myapp --cov-report=html tests\u002F\n\n# Fail if coverage below threshold\npytest --cov=myapp --cov-fail-under=80 tests\u002F\n\n# Show missing lines\npytest --cov=myapp --cov-report=term-missing tests\u002F\n```\n\nFor advanced patterns (async testing, monkeypatching, property-based testing, database testing, CI\u002FCD integration, and configuration), see [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md)\n","# Python Testing Patterns\n\nComprehensive guide to implementing robust testing strategies in Python using pytest, fixtures, mocking, parameterization, and test-driven development practices.\n\n## When to Use This Skill\n\n- Writing unit tests for Python code\n- Setting up test suites and test infrastructure\n- Implementing test-driven development (TDD)\n- Creating integration tests for APIs and services\n- Mocking external dependencies and services\n- Testing async code and concurrent operations\n- Setting up continuous testing in CI\u002FCD\n- Implementing property-based testing\n- Testing database operations\n- Debugging failing tests\n\n## Core Concepts\n\n### 1. Test Types\n\n- **Unit Tests**: Test individual functions\u002Fclasses in isolation\n- **Integration Tests**: Test interaction between components\n- **Functional Tests**: Test complete features end-to-end\n- **Performance Tests**: Measure speed and resource usage\n\n### 2. Test Structure (AAA Pattern)\n\n- **Arrange**: Set up test data and preconditions\n- **Act**: Execute the code under test\n- **Assert**: Verify the results\n\n### 3. Test Coverage\n\n- Measure what code is exercised by tests\n- Identify untested code paths\n- Aim for meaningful coverage, not just high percentages\n\n### 4. Test Isolation\n\n- Tests should be independent\n- No shared state between tests\n- Each test should clean up after itself\n\n## Quick Start\n\n```python\n# test_example.py\ndef add(a, b):\n    return a + b\n\ndef test_add():\n    \"\"\"Basic test example.\"\"\"\n    result = add(2, 3)\n    assert result == 5\n\ndef test_add_negative():\n    \"\"\"Test with negative numbers.\"\"\"\n    assert add(-1, 1) == 0\n\n# Run with: pytest test_example.py\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Testing Best Practices\n\n### Test Organization\n\n```python\n# tests\u002F\n#   __init__.py\n#   conftest.py           # Shared fixtures\n#   test_unit\u002F            # Unit tests\n#     test_models.py\n#     test_utils.py\n#   test_integration\u002F     # Integration tests\n#     test_api.py\n#     test_database.py\n#   test_e2e\u002F            # End-to-end tests\n#     test_workflows.py\n```\n\n### Test Naming Convention\n\nA common pattern: `test_\u003Cunit>_\u003Cscenario>_\u003Cexpected_outcome>`. Adapt to your team's preferences.\n\n```python\n# Pattern: test_\u003Cunit>_\u003Cscenario>_\u003Cexpected>\ndef test_create_user_with_valid_data_returns_user():\n    ...\n\ndef test_create_user_with_duplicate_email_raises_conflict():\n    ...\n\ndef test_get_user_with_unknown_id_returns_none():\n    ...\n\n# Good test names - clear and descriptive\ndef test_user_creation_with_valid_data():\n    \"\"\"Clear name describes what is being tested.\"\"\"\n    pass\n\ndef test_login_fails_with_invalid_password():\n    \"\"\"Name describes expected behavior.\"\"\"\n    pass\n\ndef test_api_returns_404_for_missing_resource():\n    \"\"\"Specific about inputs and expected outcomes.\"\"\"\n    pass\n\n# Bad test names - avoid these\ndef test_1():  # Not descriptive\n    pass\n\ndef test_user():  # Too vague\n    pass\n\ndef test_function():  # Doesn't explain what's tested\n    pass\n```\n\n### Testing Retry Behavior\n\nVerify that retry logic works correctly using mock side effects.\n\n```python\nfrom unittest.mock import Mock\n\ndef test_retries_on_transient_error():\n    \"\"\"Test that service retries on transient failures.\"\"\"\n    client = Mock()\n    # Fail twice, then succeed\n    client.request.side_effect = [\n        ConnectionError(\"Failed\"),\n        ConnectionError(\"Failed\"),\n        {\"status\": \"ok\"},\n    ]\n\n    service = ServiceWithRetry(client, max_retries=3)\n    result = service.fetch()\n\n    assert result == {\"status\": \"ok\"}\n    assert client.request.call_count == 3\n\ndef test_gives_up_after_max_retries():\n    \"\"\"Test that service stops retrying after max attempts.\"\"\"\n    client = Mock()\n    client.request.side_effect = ConnectionError(\"Failed\")\n\n    service = ServiceWithRetry(client, max_retries=3)\n\n    with pytest.raises(ConnectionError):\n        service.fetch()\n\n    assert client.request.call_count == 3\n\ndef test_does_not_retry_on_permanent_error():\n    \"\"\"Test that permanent errors are not retried.\"\"\"\n    client = Mock()\n    client.request.side_effect = ValueError(\"Invalid input\")\n\n    service = ServiceWithRetry(client, max_retries=3)\n\n    with pytest.raises(ValueError):\n        service.fetch()\n\n    # Only called once - no retry for ValueError\n    assert client.request.call_count == 1\n```\n\n### Mocking Time with Freezegun\n\nUse freezegun to control time in tests for predictable time-dependent behavior.\n\n```python\nfrom freezegun import freeze_time\nfrom datetime import datetime, timedelta\n\n@freeze_time(\"2026-01-15 10:00:00\")\ndef test_token_expiry():\n    \"\"\"Test token expires at correct time.\"\"\"\n    token = create_token(expires_in_seconds=3600)\n    assert token.expires_at == datetime(2026, 1, 15, 11, 0, 0)\n\n@freeze_time(\"2026-01-15 10:00:00\")\ndef test_is_expired_returns_false_before_expiry():\n    \"\"\"Test token is not expired when within validity period.\"\"\"\n    token = create_token(expires_in_seconds=3600)\n    assert not token.is_expired()\n\n@freeze_time(\"2026-01-15 12:00:00\")\ndef test_is_expired_returns_true_after_expiry():\n    \"\"\"Test token is expired after validity period.\"\"\"\n    token = Token(expires_at=datetime(2026, 1, 15, 11, 30, 0))\n    assert token.is_expired()\n\ndef test_with_time_travel():\n    \"\"\"Test behavior across time using freeze_time context.\"\"\"\n    with freeze_time(\"2026-01-01\") as frozen_time:\n        item = create_item()\n        assert item.created_at == datetime(2026, 1, 1)\n\n        # Move forward in time\n        frozen_time.move_to(\"2026-01-15\")\n        assert item.age_days == 14\n```\n\n### Test Markers\n\n```python\n# test_markers.py\nimport pytest\n\n@pytest.mark.slow\ndef test_slow_operation():\n    \"\"\"Mark slow tests.\"\"\"\n    import time\n    time.sleep(2)\n\n\n@pytest.mark.integration\ndef test_database_integration():\n    \"\"\"Mark integration tests.\"\"\"\n    pass\n\n\n@pytest.mark.skip(reason=\"Feature not implemented yet\")\ndef test_future_feature():\n    \"\"\"Skip tests temporarily.\"\"\"\n    pass\n\n\n@pytest.mark.skipif(os.name == \"nt\", reason=\"Unix only test\")\ndef test_unix_specific():\n    \"\"\"Conditional skip.\"\"\"\n    pass\n\n\n@pytest.mark.xfail(reason=\"Known bug #123\")\ndef test_known_bug():\n    \"\"\"Mark expected failures.\"\"\"\n    assert False\n\n\n# Run with:\n# pytest -m slow          # Run only slow tests\n# pytest -m \"not slow\"    # Skip slow tests\n# pytest -m integration   # Run integration tests\n```\n\n### Coverage Reporting\n\n```bash\n# Install coverage\npip install pytest-cov\n\n# Run tests with coverage\npytest --cov=myapp tests\u002F\n\n# Generate HTML report\npytest --cov=myapp --cov-report=html tests\u002F\n\n# Fail if coverage below threshold\npytest --cov=myapp --cov-fail-under=80 tests\u002F\n\n# Show missing lines\npytest --cov=myapp --cov-report=term-missing tests\u002F\n```\n\nFor advanced patterns (async testing, monkeypatching, property-based testing, database testing, CI\u002FCD integration, and configuration), see [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md)\n",{"name":5,"description":7},"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fpython-development\u002Fskills\u002Fpython-testing-patterns","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill python-testing-patterns",{"tool":38,"command":39},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill python-testing-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill python-testing-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-testing-patterns\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fadvanced-patterns.md","REFERENCE","参考文档",9454,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-testing-patterns\u002Freferences\u002Fadvanced-patterns.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fdetails.md",9261,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpython-development\u002Fskills\u002Fpython-testing-patterns\u002Freferences\u002Fdetails.md",[57,63,70,77,84,91],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]