Deprecate or replace a public member of Nice3point.Revit.Extensions without breaking downstream consumers, using [Obsolete] with a JetBrains CodeTemplate auto-conversion pattern.
$ npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Nice3point/RevitExtensions revit-extensions-backward-compat --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Nice3point/RevitExtensions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/revit-extensions-backward-compat .claude/skills/revit-extensions-backward-compat && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "revit-extensions-backward-compat" agent skill from https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compat into .claude/skills/revit-extensions-backward-compat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revit-extensions-backward-compat", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compatType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Nice3point/RevitExtensions revit-extensions-backward-compat --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nice3point/RevitExtensions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/revit-extensions-backward-compat .agents/skills/revit-extensions-backward-compat && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "revit-extensions-backward-compat" agent skill from https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compat into .agents/skills/revit-extensions-backward-compat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revit-extensions-backward-compat", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Nice3point/RevitExtensions revit-extensions-backward-compat --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nice3point/RevitExtensions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/revit-extensions-backward-compat .cursor/skills/revit-extensions-backward-compat && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "revit-extensions-backward-compat" agent skill from https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compat into .cursor/skills/revit-extensions-backward-compat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revit-extensions-backward-compat", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Nice3point/RevitExtensions.git --path .agents/skills/revit-extensions-backward-compat--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Nice3point/RevitExtensions revit-extensions-backward-compat --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nice3point/RevitExtensions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/revit-extensions-backward-compat .gemini/skills/revit-extensions-backward-compat && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "revit-extensions-backward-compat" agent skill from https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compat into .gemini/skills/revit-extensions-backward-compat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revit-extensions-backward-compat", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Nice3point/RevitExtensions revit-extensions-backward-compatInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Nice3point/RevitExtensions.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/revit-extensions-backward-compat .github/skills/revit-extensions-backward-compat && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "revit-extensions-backward-compat" agent skill from https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compat into .github/skills/revit-extensions-backward-compat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revit-extensions-backward-compat", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Nice3point/RevitExtensions revit-extensions-backward-compat --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nice3point/RevitExtensions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/revit-extensions-backward-compat .opencode/skills/revit-extensions-backward-compat && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "revit-extensions-backward-compat" agent skill from https://github.com/Nice3point/RevitExtensions/tree/main/.agents/skills/revit-extensions-backward-compat into .opencode/skills/revit-extensions-backward-compat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revit-extensions-backward-compat", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
revit-extensions-backward-compatDeprecate or replace a public member of Nice3point.Revit.Extensions without breaking downstream consumers, using [Obsolete] with a JetBrains CodeTemplate auto-conversion pattern.
Revit Extensions Backward Compat is an agent skill from Nice3point/RevitExtensions. Deprecate or replace a public member of Nice3point.Revit.Extensions without breaking downstream consumers, using [Obsolete] with a JetBrains CodeTemplate auto-conversion pattern. USE FOR: renaming or superseding an existing extension while keeping the old member functional; retiring a member that Revit itself deprecated in a specific year; deciding what may change on the public surface and how to migrate callers automatically. DO NOT USE FOR: authoring a brand-new extension from scratch — use…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with JetBrains IDEs and .NET. The repository describes itself as: Extensions for Revit plugin development. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e60a6bd. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
dotnetFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Revit Extensions Backward Compat loads about 2.1k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 741 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Nice3point/RevitExtensions at commit e60a6bd, republished under its MIT licence (© Nice3point). 741 words, ~2,100 tokens.
.claude/skills/revit-extensions-backward-compat/SKILL.md (or your agent's skills folder).Nice3point.Revit.Extensions is a public NuGet library with downstream consumers; its public surface is a contract.
A deleted or altered member breaks other people's builds. Keep the old member forever, mark it [Obsolete], and ship a JetBrains CodeTemplate; ReSharper and Rider then auto-migrate call sites to the replacement.
This skill covers deprecating, renaming, or superseding an existing member; it depends on JetBrains annotations (JetBrains.Annotations) for both [Obsolete]'s companion CodeTemplate and the surrounding attributes.
Keep the old member in place and add the new one in the same extension(Type) block.
Both members call the underlying Revit API directly; the new member never delegates to the old one, and the old one never delegates to the new one.
Write full method bodies; an expression-bodied property is fine for a read-only value.
extension(Element element)
{
/// <summary>Determines whether element can be mirrored</summary>
/// <returns>True if the element can be mirrored</returns>
public bool CanBeMirrored => ElementTransformUtils.CanMirrorElement(element.Document, element.Id);
}[Obsolete] with a message that names the replacementThe message states plainly what to use instead. The obsolete member keeps calling the original Revit API; it stays correct and independent and must not recurse into the new extension.
[Pure]
[Obsolete("Use CanBeMirrored() instead")]
public bool CanMirrorElement()
{
return ElementTransformUtils.CanMirrorElement(element.Document, element.Id);
}Add [CodeTemplate] beside [Obsolete] so the IDE rewrites call sites automatically.
searchTemplate matches the old call, ReplaceTemplate produces the new call, and the two Message/ReplaceMessage strings surface in the inspection and the quick-fix.
Use $expr$ for the receiver and match the replacement shape exactly — a property replacement drops the parentheses.
[Pure]
[Obsolete("Use CanBeMirrored() instead")]
[CodeTemplate(
searchTemplate: "$expr$.CanMirrorElement()",
Message = "CanMirrorElement is obsolete, use CanBeMirrored instead",
ReplaceTemplate = "$expr$.CanBeMirrored",
ReplaceMessage = "Replace with CanBeMirrored")]
public bool CanMirrorElement()
{
return ElementTransformUtils.CanMirrorElement(element.Document, element.Id);
}When the member takes arguments, thread them through the template with named placeholders; the rewrite preserves them:
[Pure]
[Obsolete("Use CanBeMirrored() instead")]
[CodeTemplate(
searchTemplate: "$expr$.CanMirrorElements($document$)",
Message = "CanMirrorElements is obsolete, use CanBeMirrored instead",
ReplaceTemplate = "$expr$.CanBeMirrored($document$)",
ReplaceMessage = "Replace with CanBeMirrored()")]
public bool CanMirrorElements(Document document)
{
return ElementTransformUtils.CanMirrorElements(document, elements);
}If the underlying Revit API is only obsolete from a given release, wrap just the [Obsolete] and [CodeTemplate] attributes in the matching #if; the member deprecates on the versions that warrant it and stays clean elsewhere.
When the replacement adds a parameter, add it as an optional argument at the end; use a $placeholder$ in the template for the new argument.
[Pure]
#if REVIT2027_OR_GREATER
[Obsolete("This method is deprecated in Revit 2027 and may be removed in a later version of Revit. We suggest you use the overload which accepts a region input instead.")]
[CodeTemplate(
searchTemplate: "$expr$.DownloadParameterOptions()",
Message = "DownloadParameterOptions() is obsolete, use overload with region parameter",
ReplaceTemplate = "$expr$.DownloadParameterOptions($arg$)",
ReplaceMessage = "Replace with DownloadParameterOptions(region)")]
#endif
public ParameterDownloadOptions DownloadParameterOptions()
{
return ParameterUtils.DownloadParameterOptions(typeId);
}Hold every change to the allowed set before you compile:
void mutation becoming its source object for chaining.Then compile every configuration from the build directory and update the shipped docs in the same change.
dotnet run -c ReleaseUpdate Readme.md, add a categorized Changelog.md entry for the deprecation, and keep the XML docs on both the old and new members.
[Obsolete] carries a message that names the replacement; no [EditorBrowsable(EditorBrowsableState.Never)] sits on an obsolete Element extension.[CodeTemplate] supplies searchTemplate, ReplaceTemplate, Message, and ReplaceMessage, and the replacement shape matches the new member (property vs. method, argument placeholders preserved).#if.dotnet run -c Release compiles every configuration and Readme.md/Changelog.md/XML docs are updated.| Pitfall | Correct approach |
|---|---|
| Deleting or renaming the old member outright | Keep it, mark it [Obsolete], and add the replacement beside it. |
| The obsolete member calling the new extension | Call the original Revit API from the obsolete member; it never recurses and stays independent. |
[EditorBrowsable(Never)] on an obsolete Element extension | Omit it; let the member stay discoverable while [Obsolete] warns. |
[Obsolete] without a [CodeTemplate] | Add the searchTemplate → ReplaceTemplate pattern; callers auto-migrate. |
ReplaceTemplate keeping parentheses for a property replacement | Match the replacement exactly — drop the () when the new member is a property. |
| Changing a signature or return type, or inserting a required parameter | Add a new member or an optional trailing parameter instead. |
| Deprecating unconditionally when Revit deprecates only in a later year | Wrap just the [Obsolete]/[CodeTemplate] attributes in the matching #if. |
© Nice3point, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/revit-extensions-backward-compat of Nice3point/RevitExtensions.
Open the folder on GitHubat commit e60a6bd
Revit Extensions Backward Compat next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Revit Extensions Backward Compat this skillNice3point/RevitExtensions | 168 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Revit Toolkit Backward CompatNice3point/RevitToolkit | 176 | — | ~2k | Automated safety check: Pass | MIT | |
| Formatplatformplatform/PlatformPlatform | 441 | — | ~445 | Automated safety check: Pass | MIT | |
| Lintplatformplatform/PlatformPlatform | 441 | — | ~632 | Automated safety check: Pass | MIT | |
| ProfileLog2n-io/Typhon | 250 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Mcaf Dotnet Resharper Cltmanagedcode/Storage | 138 | — | ~1.5k | Automated safety check: Pass | MIT |
Nice3point/RevitToolkit
Evolve the public surface of Nice3point.Revit.Toolkit without breaking downstream consumers: deprecate a renamed or replaced member with [Obsolete] with a JetBrains [CodeTemplate] auto-conversion…
platformplatform/PlatformPlatform
Auto-format code via the developer CLI - backend (.NET via JetBrains cleanupcode), frontend (oxfmt + oxlint --fix), and the developer CLI itself.
platformplatform/PlatformPlatform
Lint code via the developer CLI - backend (.NET via JetBrains inspectcode), frontend (oxlint), and the developer CLI itself.
Log2n-io/Typhon
Profile a benchmark workload with dotTrace sampling, generate an XML report, and analyze hot spots
managedcode/Storage
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories.
managedcode/dotnet-skills
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories.
Nice3point/RevitExtensions
Add a fluent extension to Nice3point.Revit.Extensions with C 14 extension(Type){} blocks that wrap the raw Revit API for readability and chaining.
Works with
Deprecate or replace a public member of Nice3point.Revit.Extensions without breaking downstream consumers, using [Obsolete] with a JetBrains CodeTemplate auto-conversion pattern. Revit Extensions Backward Compat is an agent skill from Nice3point/RevitExtensions.Extensions without breaking downstream consumers, using [Obsolete] with a JetBrains CodeTemplate auto-conversion pattern.
Revit Extensions Backward Compat fits situations like: superseding an existing extension while keeping the old member functional; retiring a member that Revit itself deprecated in a specific year; deciding what may change on the public surface and how to migrate callers automatically; : authoring a brand-new extension from scratch — use revit-extensions-authoring.
Run `npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a claude-code`. Or copy the skill folder (.agents/skills/revit-extensions-backward-compat in Nice3point/RevitExtensions) into .claude/skills/revit-extensions-backward-compat in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a codex`. Or copy the skill folder (.agents/skills/revit-extensions-backward-compat in Nice3point/RevitExtensions) into .agents/skills/revit-extensions-backward-compat in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nice3point/RevitExtensions --skill revit-extensions-backward-compat -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/revit-extensions-backward-compat, .gemini/skills/revit-extensions-backward-compat, .github/skills/revit-extensions-backward-compat and .opencode/skills/revit-extensions-backward-compat in your project.
Going by SKILL.md and its folder, Revit Extensions Backward Compat needs the command-line tools its instructions call (dotnet).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Revit Extensions Backward Compat is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Revit Extensions Backward Compat: Revit Toolkit Backward Compat (Nice3point/RevitToolkit, 176 stars), Format (platformplatform/PlatformPlatform, 441 stars), Lint (platformplatform/PlatformPlatform, 441 stars) and Profile (Log2n-io/Typhon, 250 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Nice3point (a GitHub user) maintains it in Nice3point/RevitExtensions, which has 168 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: Nice3point/RevitExtensions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
