Nclat Appeal Section 61 Ibc Draft
Draft a Memorandum of Appeal before the National Company Law Appellate Tribunal under Section 61 of the Insolvency and Bankruptcy Code 2016 read with the NCLAT Rules 2016, from an order of the National Company Law Tribunal made under the IBC (admission / rejection of Section 7 / 9 / 10 application, approval of resolution plan under Section 31, liquidation order under Section 33, IRP / RP / liquidator-related disputes, voidable-transaction orders under Sections 43-51, avoidance-transaction orders, personal-guarantor IRP orders under Section 100, distribution of liquidation proceeds, or any other NCLT order under the IBC). …
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Install (Claude Code):
cp -r nclat-appeal-section-61-ibc-draft ~/.claude/skills/- Adoption: 1 repos
- Upkeep: 79.0
- Freshness: 94.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- Contributors: 2
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
Its own instructions
Its SKILL.md states a limitation.
Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
source ↗ · skill:Wolfgangrush/nclat-appeal-section-61-ibc-draft
Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-16 · scorer s5 · how · something wrong here?