[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6CSX71V0CDN5701B41VKB":3,"skill-same:01M7F6CSX71V0CDN5701B41VKB":63},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7F6CSX71V0CDN5701B41VKB","analyzing-covenant-compliance",null,"Reviews financial covenant compliance calculations with cure provisions and default trigger analysis. Use when checking covenant compliance, calculating coverage ratios, or evaluating covenant headroom.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fanalyzing-covenant-compliance\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: analyzing-covenant-compliance\nlanguage: en\ndescription: Reviews financial covenant compliance calculations with cure provisions and default trigger analysis. Use when checking covenant compliance, calculating coverage ratios, or evaluating covenant headroom.\ntags:\n  - analysis\n  - fixed-income\n  - compliance\nmetadata:\n  author: casemark\n  practice_areas:\n    - Fixed Income\n    - Credit Research\n    - Bond Trading\n  document_types:\n    - Analysis Report\n  skill_modes:\n    - Analysis\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fanalyzing-covenant-compliance\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Analyzing Covenant Compliance\n\n## When To Use\n\n- Evaluating whether a bond issuer or borrower is in compliance with financial maintenance covenants (leverage ratio, interest coverage, fixed charge coverage, minimum net worth, etc.)\n- Calculating covenant headroom to assess proximity to a potential default trigger\n- Reviewing cure provisions (equity cure rights, add-back mechanics) and their remaining availability\n- Assessing the impact of a proposed transaction (acquisition, dividend, asset sale) on incurrence covenants\n- Preparing credit surveillance reports or event-driven covenant analysis for trading decisions\n\n## Inputs To Gather\n\n- **Credit agreement or indenture** — the governing document containing covenant definitions, calculation mechanics, and cure provisions\n- **Financial statements** — most recent quarterly\u002Fannual financials (income statement, balance sheet, cash flow statement) as delivered under the credit agreement\n- **Compliance certificate** — borrower's own covenant compliance certificate if available, with management's calculations\n- **Permitted adjustments schedule** — EBITDA add-backs, pro forma adjustments for acquisitions\u002Fdispositions, and any run-rate synergies claimed\n- **Cure history** — record of any prior equity cures exercised, with amounts and dates\n- **Amendment\u002Fwaiver history** — any covenant amendments, holidays, or waivers that modify baseline thresholds\n\n## Workflow\n\n1. **Map covenant definitions to financials**\n   - Identify each financial maintenance and incurrence covenant (e.g., Total Leverage Ratio, Interest Coverage Ratio, Fixed Charge Coverage Ratio, Minimum Liquidity)\n   - Extract the precise calculation methodology from the credit agreement — note defined terms for \"Consolidated EBITDA,\" \"Consolidated Total Debt,\" \"Net Debt,\" etc.\n   - Flag any definitional mismatches between the borrower's compliance certificate and the governing document [VERIFY]\n\n2. **Recalculate each covenant ratio independently**\n   - Compute trailing-twelve-month (TTM) or last-quarter-annualized figures as specified by the agreement\n   - Apply permitted add-backs and pro forma adjustments — verify each add-back against the cap or basket limit in the credit agreement\n   - Calculate the ratio using the agreement's numerator\u002Fdenominator definitions, not generic financial metrics\n   - Compare your result to the borrower's reported compliance certificate figure; investigate any variance exceeding 0.05x\n\n3. **Assess covenant headroom**\n   - For each covenant, calculate the cushion between actual performance and the trigger threshold (in absolute terms and as a percentage)\n   - Model sensitivity: determine how much EBITDA decline, debt increase, or revenue shortfall would trip each covenant\n   - Identify the tightest covenant — this is the binding constraint and the focus of default-risk analysis\n   - Flag any step-down or step-up schedules that tighten thresholds in upcoming periods [VERIFY]\n\n4. **Evaluate cure provisions and default triggers**\n   - Determine whether equity cure rights exist and their terms: maximum number of cures per term, consecutive-quarter limits, minimum cure amount, deemed EBITDA treatment vs. debt paydown\n   - Count remaining cure capacity (cures used vs. total permitted)\n   - Assess whether a potential breach would trigger a cross-default to other facilities or bond indentures\n   - Review grace periods and notice requirements before a covenant breach becomes an event of default [VERIFY]\n\n5. **Analyze incurrence covenants for proposed transactions**\n   - For asset sales, restricted payments, or additional debt, test whether the proposed action satisfies the applicable incurrence test (e.g., pro forma leverage ≤ threshold, Fixed Charge Coverage ≥ 2.0x)\n   - Verify basket availability and capacity (general basket, builder basket, available amount)\n   - Confirm whether the transaction uses a ratio-based exception or a flat-dollar basket\n\n6. **Summarize findings and risk flags**\n   - Present a covenant compliance summary table with: covenant name, required threshold, actual result, headroom, and pass\u002Ffail status\n   - Highlight any covenant within 10% of its trigger as \"watch\" status\n   - Note any reliance on contested add-backs, aggressive pro forma adjustments, or unusual definitional interpretations\n\n## Output\n\n- **Covenant Compliance Summary Table** — covenant name | definition reference (section #) | required threshold | actual ratio | headroom | status (Pass \u002F Watch \u002F Breach)\n- **Headroom Sensitivity Analysis** — for the tightest covenant, show breakeven EBITDA decline and incremental debt capacity\n- **Cure Provision Status** — cures exercised, cures remaining, conditions for exercise\n- **Risk Flags** — list of items requiring attention: approaching thresholds, aggressive add-backs, upcoming step-downs, cross-default exposure\n- **Recommended Actions** — monitoring frequency, amendment considerations, or trading implications\n\n## Quality Checks\n\n- Every ratio recalculation ties back to specific line items in the financial statements with clear sourcing\n- Defined terms match the credit agreement exactly — do not substitute generic financial definitions\n- Add-back caps and basket limits are verified against agreement language, not approximated\n- Cure provision analysis accounts for all contractual limitations (frequency, amount, deemed treatment)\n- Any jurisdiction-specific enforceability issues (e.g., intercreditor agreement override, local insolvency law implications) are flagged with [VERIFY]\n- Headroom calculations use the correct testing period and step-down schedule for the relevant quarter\n- Cross-default provisions are identified across all related facilities and indentures\n","# Analyzing Covenant Compliance\n\n## When To Use\n\n- Evaluating whether a bond issuer or borrower is in compliance with financial maintenance covenants (leverage ratio, interest coverage, fixed charge coverage, minimum net worth, etc.)\n- Calculating covenant headroom to assess proximity to a potential default trigger\n- Reviewing cure provisions (equity cure rights, add-back mechanics) and their remaining availability\n- Assessing the impact of a proposed transaction (acquisition, dividend, asset sale) on incurrence covenants\n- Preparing credit surveillance reports or event-driven covenant analysis for trading decisions\n\n## Inputs To Gather\n\n- **Credit agreement or indenture** — the governing document containing covenant definitions, calculation mechanics, and cure provisions\n- **Financial statements** — most recent quarterly\u002Fannual financials (income statement, balance sheet, cash flow statement) as delivered under the credit agreement\n- **Compliance certificate** — borrower's own covenant compliance certificate if available, with management's calculations\n- **Permitted adjustments schedule** — EBITDA add-backs, pro forma adjustments for acquisitions\u002Fdispositions, and any run-rate synergies claimed\n- **Cure history** — record of any prior equity cures exercised, with amounts and dates\n- **Amendment\u002Fwaiver history** — any covenant amendments, holidays, or waivers that modify baseline thresholds\n\n## Workflow\n\n1. **Map covenant definitions to financials**\n   - Identify each financial maintenance and incurrence covenant (e.g., Total Leverage Ratio, Interest Coverage Ratio, Fixed Charge Coverage Ratio, Minimum Liquidity)\n   - Extract the precise calculation methodology from the credit agreement — note defined terms for \"Consolidated EBITDA,\" \"Consolidated Total Debt,\" \"Net Debt,\" etc.\n   - Flag any definitional mismatches between the borrower's compliance certificate and the governing document [VERIFY]\n\n2. **Recalculate each covenant ratio independently**\n   - Compute trailing-twelve-month (TTM) or last-quarter-annualized figures as specified by the agreement\n   - Apply permitted add-backs and pro forma adjustments — verify each add-back against the cap or basket limit in the credit agreement\n   - Calculate the ratio using the agreement's numerator\u002Fdenominator definitions, not generic financial metrics\n   - Compare your result to the borrower's reported compliance certificate figure; investigate any variance exceeding 0.05x\n\n3. **Assess covenant headroom**\n   - For each covenant, calculate the cushion between actual performance and the trigger threshold (in absolute terms and as a percentage)\n   - Model sensitivity: determine how much EBITDA decline, debt increase, or revenue shortfall would trip each covenant\n   - Identify the tightest covenant — this is the binding constraint and the focus of default-risk analysis\n   - Flag any step-down or step-up schedules that tighten thresholds in upcoming periods [VERIFY]\n\n4. **Evaluate cure provisions and default triggers**\n   - Determine whether equity cure rights exist and their terms: maximum number of cures per term, consecutive-quarter limits, minimum cure amount, deemed EBITDA treatment vs. debt paydown\n   - Count remaining cure capacity (cures used vs. total permitted)\n   - Assess whether a potential breach would trigger a cross-default to other facilities or bond indentures\n   - Review grace periods and notice requirements before a covenant breach becomes an event of default [VERIFY]\n\n5. **Analyze incurrence covenants for proposed transactions**\n   - For asset sales, restricted payments, or additional debt, test whether the proposed action satisfies the applicable incurrence test (e.g., pro forma leverage ≤ threshold, Fixed Charge Coverage ≥ 2.0x)\n   - Verify basket availability and capacity (general basket, builder basket, available amount)\n   - Confirm whether the transaction uses a ratio-based exception or a flat-dollar basket\n\n6. **Summarize findings and risk flags**\n   - Present a covenant compliance summary table with: covenant name, required threshold, actual result, headroom, and pass\u002Ffail status\n   - Highlight any covenant within 10% of its trigger as \"watch\" status\n   - Note any reliance on contested add-backs, aggressive pro forma adjustments, or unusual definitional interpretations\n\n## Output\n\n- **Covenant Compliance Summary Table** — covenant name | definition reference (section #) | required threshold | actual ratio | headroom | status (Pass \u002F Watch \u002F Breach)\n- **Headroom Sensitivity Analysis** — for the tightest covenant, show breakeven EBITDA decline and incremental debt capacity\n- **Cure Provision Status** — cures exercised, cures remaining, conditions for exercise\n- **Risk Flags** — list of items requiring attention: approaching thresholds, aggressive add-backs, upcoming step-downs, cross-default exposure\n- **Recommended Actions** — monitoring frequency, amendment considerations, or trading implications\n\n## Quality Checks\n\n- Every ratio recalculation ties back to specific line items in the financial statements with clear sourcing\n- Defined terms match the credit agreement exactly — do not substitute generic financial definitions\n- Add-back caps and basket limits are verified against agreement language, not approximated\n- Cure provision analysis accounts for all contractual limitations (frequency, amount, deemed treatment)\n- Any jurisdiction-specific enforceability issues (e.g., intercreditor agreement override, local insolvency law implications) are flagged with [VERIFY]\n- Headroom calculations use the correct testing period and step-down schedule for the relevant quarter\n- Cross-default provisions are identified across all related facilities and indentures\n",{"name":5,"tags":24,"source":28,"license":15,"language":29,"metadata":30,"description":7,"imported_at":40,"source_path":41,"source_repository":42},[25,26,27],"analysis","fixed-income","compliance","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":31,"skill_modes":32,"document_types":34,"practice_areas":36},"casemark",[33],"Analysis",[35],"Analysis Report",[37,38,39],"Fixed Income","Credit Research","Bond Trading","2026-09-20","skills\u002Ffinance\u002Fanalyzing-covenant-compliance\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fanalyzing-covenant-compliance","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analyzing-covenant-compliance",{"tool":55,"command":56},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analyzing-covenant-compliance",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analyzing-covenant-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fanalyzing-covenant-compliance\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]