resolving-ewis

resolving-ewis is a skill for Claude Code from sfc-gh-dflippo/snowflake-dbt-demo. It costs 75 tokens per session (511 once invoked), scanned A, original, Apache-2.0.

A guidance step for handling an EWI code, which is a warning identifier produced during SQL conversion. It looks for documented guidance, applies the fix, and records new solutions when needed.

In plain words
What is it for?
Use it when a converted SQL object contains an EWI code, such as SSC-EWI-0021, that needs investigation and correction.
Why use it?
It gives conversion warnings a repeatable resolution process instead of leaving each error for separate investigation. It also preserves fixes and examples for later occurrences.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the snowflake-migration plugin — 72 skills, 7 agents shipped together

Good fit Use it when a converted SQL object contains an EWI code, such as SSC-EWI-0021, that needs investigation and correction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add sfc-gh-dflippo/snowflake-dbt-demo --skill resolving-ewis
Clone the repo
git clone --depth 1 https://github.com/sfc-gh-dflippo/snowflake-dbt-demo

Made for: Claude Code.

Or install snowflake-migration, the plugin that ships this one along with the rest of its 72 skills, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for resolving-ewis

README.md
[![agentmods](https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis/github.svg)](https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis)
Your own site
<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for resolving-ewis

Your own site · 80×15
<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.00511
Opus 5 $0.00037 $0.00255
Sonnet 5 $0.00015 $0.00102
Haiku 4.5 $0.00007 $0.00051

Measured 2d ago against content hash b46f2affe121, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

resolving-ewis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/snowflake-migration/skills/migration/migrate-objects/rule-engine/resolving-ewis/SKILL.md · 78 lines

What it actually says

Usage

When you encounter an EWI code (e.g., SSC-EWI-0021, SSC-EWI-TS0087):

  1. Check for existing reference: Look in the reference/ folder for a file matching the EWI code (e.g., reference/SSC-EWI-0021.md)

  2. If the reference exists:

    • Read and follow the guidance in the reference file
    • Apply the documented fix patterns to resolve the EWI
    • After successfully resolving the issue, update the reference file with any new learnings, edge cases, or patterns discovered
  3. If the reference does not exist:

    • Resolve the EWI using your knowledge of SQL Server and Snowflake
    • After successfully resolving the issue, create a new reference file (e.g., reference/SSC-EWI-XXXX.md)
    • Document the problem, fix patterns, examples, and any important considerations

Reference File Structure

Each reference file should follow this structure:

# SSC-EWI-XXXX - Brief Description

Brief explanation of what this EWI means and why it occurs.

## Quick Reference

| SQL Server | Snowflake |
|------------|-----------|
| Original syntax | Converted syntax |

## Identification

How to identify this EWI in code (markers, patterns).

## Fix Process

Step-by-step process to resolve the EWI.

## Examples

### Before
```sql
-- Invalid/unconverted code

After

-- Valid Snowflake code

Key Points

  • Important considerations
  • Edge cases
  • Common mistakes to avoid

Resources

  • Links to relevant Snowflake documentation
  • Links to relevant SQL Server documentation

## Updating References

When updating an existing reference after resolving an EWI:

- Add new patterns or edge cases discovered
- Include additional examples if the fix was non-obvious
- Document any gotchas or pitfalls encountered
- Keep the file focused and well-organized
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 78 lines · 75 tokens per session scan A b46f2affe121

Subscribe to this mod's changes

resolving-ewis is a skill published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 511 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.

Related

Other skills, from other repositories

reproduce-bug

Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…

googleapis/mcp-toolbox · 130 tokens

fix-failing-tests

Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…

googleapis/mcp-toolbox · 87 tokens

triage-issues

Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…

googleapis/mcp-toolbox · 164 tokens

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…

prowler-cloud/prowler · 108 tokens

graphjin-eval

Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.

dosco/graphjin · 27 tokens

axiom-audit-grdb-performance

Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.

CharlesWiltgen/Axiom · 43 tokens