# Maf Obsolete Api Registry

> Machine-readable registry of known CS0618 obsolete API warnings for MAF migrations. Each entry maps an obsolete method signature to its replacement, with the exact fix pattern. Prefer the MCP tool MafRegistryLookup (by ID) or MafApiSafety (by symbol) for one-shot queries; this skill is for understanding the registry schema and contributing new entries. Load this skill when cs0618-hunter has ident…

- **Type:** Skill
- **Install:** `agentstack add skill-joslat-maf-doctor-maf-obsolete-api-registry`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [joslat](https://agentstack.voostack.com/s/joslat)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [joslat](https://github.com/joslat)
- **Source:** https://github.com/joslat/maf-doctor/tree/main/.github/skills/maf-obsolete-api-registry

## Install

```sh
agentstack add skill-joslat-maf-doctor-maf-obsolete-api-registry
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Obsolete API Registry

This registry is the source of truth for all known `[Obsolete]` APIs in MAF 1.3.0.

## How to Use This Skill

1. A `cs0618-hunter` scan has produced one or more CS0618 warning lines
2. Extract the **obsolete method name** from the warning text
3. Look it up in `registry.yaml` (in this directory)
4. Apply the `replacement_pattern` exactly as documented
5. If the warning is NOT in the registry — add it (see "Adding New Entries" below)

## registry.yaml Format

```yaml
- id: 
  package: 
  version_introduced: 
  type: 
  method: 
  obsolete_signature: 
  replacement_signature: 
  argument_order_change: 
  fix_description: 
  example_before: |
    
  example_after: |
    
  cs_warning: CS0618
  guide_section: 
  notes: 
```

## Adding New Entries

When `cs0618-hunter` finds a CS0618 warning that is NOT in `registry.yaml`:

1. Open `registry.yaml`
2. Add a new entry using the format above
3. Fill in the obsolete and replacement signatures from the compiler warning message
4. Test the fix — confirm the warning disappears after applying it
5. Commit the updated `registry.yaml` alongside your migration changes

This is how the registry grows over time — each migration run that finds a new obsolete API enriches the registry for future runs.

---

## Current Registry Contents

See `registry.yaml` for the full machine-readable data. Current entries:

| ID | Method | Obsolete signature | Replacement |
|----|--------|--------------------|-------------|
| `MAF130-FAN-IN-001` | `WorkflowBuilder.AddFanInBarrierEdge` | `(ExecutorBinding target, IEnumerable sources)` | `(IEnumerable sources, ExecutorBinding target)` |

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [joslat](https://github.com/joslat)
- **Source:** [joslat/maf-doctor](https://github.com/joslat/maf-doctor)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-joslat-maf-doctor-maf-obsolete-api-registry
- Seller: https://agentstack.voostack.com/s/joslat
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.