New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Code Completion

by facioquo in facioquo/stock-indicators-dotnet

Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the…

Apache-2.0Auto-check passedTesting & QA

Install Code Completion

skills CLI
$ npx skills add facioquo/stock-indicators-dotnet --skill code-completion -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install facioquo/stock-indicators-dotnet code-completion --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/facioquo/stock-indicators-dotnet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-completion .claude/skills/code-completion && rm -rf skills-src

Use ~/.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/

Facts

Skill name
code-completion
GitHub stars
1.2k
Token cost
~1.2k tokens
SKILL.md length
500 words
Files
2 (incl. references)
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the…

  • Works in 6 steps: Remove dead code → Apply fixers → Build → …
  • Tasks that involve Unit testing
  • SKILL.md covers Workflow, Migration shims, Indicator work and Quality bar, plus 1 more section
  • Calls dotnet, npx and bash

What it does

Code Completion is an agent skill from facioquo/stock-indicators-dotnet. Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the exact commands and VS Code task names CI mirrors. Use before reporting any implementation, bug fix, or refactor as done, before committing, and when a CI quick-check, lint, or build step fails.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/quality-gates.md`).

It sits in Testing & QA, covering Unit testing, Quality gates and Debugging. It works with Visual Studio Code and .NET. The repository describes itself as: Stock Indicators for .NET is a C NuGet package that transforms raw equity, commodity, forex, or cryptocurrency financial market price quotes into technical indicators and trading… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Unit testing
  • Tasks that involve Quality gates
  • Tasks that involve Debugging

Example prompts

  • “/code-completion”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Remove dead code
  2. Apply fixers
  3. Build
  4. Run unit tests
  5. Update documentation and migration shims
  6. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit e439ae4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet
    • npx
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Completion loads about 1.2k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 500 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from facioquo/stock-indicators-dotnet at commit e439ae4, republished under its Apache-2.0 licence (© facioquo). 500 words, ~1,166 tokens.

Download SKILL.mdSave it as .claude/skills/code-completion/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
code-completion
description
Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the exact commands and VS Code task names CI mirrors. Use before reporting any implementation, bug fix, or refactor as done, before committing, and when a CI quick-check, lint, or build step fails.

Code completion

Run these gates before reporting any implementation cycle as done. Every command, CI-equivalent, VS Code task label, and configuration file location is in the quality gates reference; load it when a gate fails or you need a single-gate command.

CI builds src/Indicators.csproj and tests/Library/Tests.Indicators.csproj with -warnAsError, so a warning that passes a local build fails CI.

Workflow

Step 1: Remove dead code
  • Delete commented-out code, unused usings, variables, and helpers.
  • Strip debugging aids such as Console.WriteLine calls.
  • Delete scratch files (.bak, .new, .debug.*).
Step 2: Apply fixers

Run the fixers:

bash
dotnet tool run roslynator fix --properties TargetFramework=net10.0 --severity-level hidden --verbosity normal
dotnet format --severity info --no-restore
echo y | npx markdownlint-cli2 --fix

VS Code task: Lint: All (fix) (it builds first). The Roslynator CLI comes from dotnet-tools.json; run dotnet tool restore first if roslynator is not found.

Step 3: Build
bash
dotnet build "Stock.Indicators.sln" -v minimal --nologo

VS Code task: Build: .NET Solution (incremental). Zero warnings and zero errors.

Step 4: Run unit tests
bash
dotnet test tests/Library/Tests.Indicators.csproj --no-restore --nologo --settings tests/tests.unit.runsettings

VS Code task: Test: Unit tests. The runsettings filter excludes the Regression and Integration test categories. Run Test: Regression tests as well when an indicator's calculation changed.

Step 5: Update documentation and migration shims

When a public API or indicator behavior changes:

  • Update XML documentation on every changed public member.
  • Update the indicator page docs/indicators/{slug}.md — the documentation skill owns its structure.
  • Rename or remove a public v3 API only behind a delegating shim — see migration shims.
Step 6: Verify

Run the read-only checks CI runs, and confirm each exits clean:

bash
dotnet tool run roslynator analyze --properties TargetFramework=net10.0 --severity-level hidden --verbosity normal
dotnet format --verify-no-changes --severity info --no-restore
echo y | npx markdownlint-cli2

VS Code task: Verify: Quick checks (build + lint + unit test) covers build, Roslynator, markdownlint, and unit tests; it does not run dotnet format --verify-no-changes (Lint: .NET format does). When a {Name}Hub.cs or its test changed, also run bash tools/scripts/audit-streamhub.sh, which CI runs in the quick check.

Show full SKILL.md (227 more words)Show less

Migration shims

Obsolete members live in src/Obsolete/, each [Obsolete] with a message naming the replacement and [ExcludeFromCodeCoverage]:

FileHolds
Obsolete.V3.Indicators.csv2 → v3 indicator method renames (GetX → ToX)
Obsolete.V3.Other.csOther v2 → v3 type and utility bridges
Obsolete.V3.Suppressions.csAssembly-level analyzer suppressions the shims need
Obsolete.V4.csNon-breaking shims for public APIs renamed within v3; removed in v4
  • A v2 → v3 change also updates docs/migration/v3.md.
  • A rename within v3 adds a delegating member to Obsolete.V4.cs with [Obsolete("Use … instead.", false)], so existing callers compile with a warning.

Indicator work

A new or changed indicator has a per-style file set (series, buffer, stream, catalog, tests, regression baseline, benchmark, docs page). The indicator-series skill owns that checklist; this skill adds only the gates above.

Quality bar

  • Zero lint findings, build warnings, and build errors.
  • All unit tests pass; the repository targets ≥ 98% line coverage, reported to Codacy from CI.
  • Public API changes carry XML docs, an updated docs page, and a migration shim.

Do not do these

  • Do not suppress, ignore, or defer a warning to get a gate green; fix the cause.
  • Do not run dotnet test "Stock.Indicators.sln" as the unit gate. It also runs the regression and integration categories, which are slow and spawn the SSE test server process.
  • Do not report work as done from a build alone; the unit tests and the read-only lint checks are part of the bar.

© facioquo, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/code-completion of facioquo/stock-indicators-dotnet.

  • SKILL.md
  • references/quality-gates.md

Open the folder on GitHubat commit e439ae4

Compare with similar skills

Code Completion 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.

Code Completion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Completion this skillfacioquo/stock-indicators-dotnet1.2k—~1.2kAutomated safety check: PassApache-2.0
Chrome Devtools MCPmanagedcode/dotnet-skills486—~2.2kAutomated safety check: PassMIT
Debug Surefireeclipse-rdf4j/rdf4j420—~2.4kAutomated safety check: PassBSD-3-Clause
Odc DebuggingDouglasNeuroInformatics/OpenDataCapture119—~2.8kAutomated safety check: NotesApache-2.0
Adk Setupgoogle/adk-python22k—~993Automated safety check: NotesApache-2.0
Checkav1155/houndarr292—~366Automated safety check: PassAGPL-3.0

Similar skills

  • Chrome Devtools MCP

    managedcode/dotnet-skills

    Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client.

    486 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Debug Surefire

    eclipse-rdf4j/rdf4j

    Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…

    420 GitHub stars~2.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Odc Debugging

    DouglasNeuroInformatics/OpenDataCapture

    What actually breaks in Open Data Capture — a failing build, lint, unit test or e2e run; a change with no visible effect; a suite that stays green after you broke the code on purpose; an error…

    119 GitHub stars~2.8k tokensUpdated today
    Testing & QAAuto-check: notes

  • Adk Setup

    google/adk-python

    Official

    Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…

    22k GitHub stars~993 tokensUpdated today
    DevelopmentAuto-check: notes

  • Check

    av1155/houndarr

    Run Houndarr's full quality gate (ruff lint, ruff format check, mypy, bandit, pytest) and report results in a single table.

    292 GitHub stars~366 tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Validate

    juliepy/AI-Engineer-from-scrach

    Run the full quality gate (ruff + mypy + pytest + tsc + vitest) and report PASS/FAIL for each command.

    433 GitHub stars~500 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from facioquo/stock-indicators-dotnet

All 10 skills in this repo

  • Markdown

    facioquo/stock-indicators-dotnet

    Format and lint Markdown in this repository against GitHub Flavored Markdown and its markdownlint-cli2 configuration — headers, lists, code fences, callouts (VitePress containers on docs-site pages…

    1.2k GitHub stars~812 tokensUpdated today
    Auto-check passed

  • Indicator Series

    facioquo/stock-indicators-dotnet

    Implement Series-style batch indicators (To{Name}() in {Name}.Series.cs), the canonical numerical reference every BufferList and StreamHub must match exactly.

    1.2k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Indicator Stream

    facioquo/stock-indicators-dotnet

    Implement StreamHub real-time indicators — base-class choice (ChainHub, BarProvider, StreamHub), constructor and ToIndicator conventions, RollbackState overrides, per-tick performance rules…

    1.2k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Performance Testing

    facioquo/stock-indicators-dotnet

    Benchmark indicators with BenchmarkDotNet in tools/performance — add Series, Buffer, Stream, and style-comparison benchmarks, spot-check one indicator against committed baselines, evaluate the full…

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Documentation

    facioquo/stock-indicators-dotnet

    Author indicator reference pages on the VitePress documentation site — page section order, parameter and result tables, warmup and convergence wording, chaining and streaming examples, the…

    1.2k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Indicator Buffer

    facioquo/stock-indicators-dotnet

    Implement BufferList incremental indicators ({Name}List, a BufferList<TResult subclass) — increment interface choice, constructor and To{Name}List() conventions, rolling-buffer helpers, pruning and…

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Code Completion

What does Code Completion do?

Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the…. Code Completion is an agent skill from facioquo/stock-indicators-dotnet. Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the exact commands and VS Code task names CI mirrors.

When should I use Code Completion?

Code Completion fits situations like: tasks that involve Unit testing; tasks that involve Quality gates; tasks that involve Debugging.

How do I install Code Completion in Claude Code?

Run `npx skills add facioquo/stock-indicators-dotnet --skill code-completion -a claude-code`. Or copy the skill folder (.agents/skills/code-completion in facioquo/stock-indicators-dotnet) into .claude/skills/code-completion in your project. Claude Code loads it when a task matches its description.

How do I install Code Completion in Codex?

Run `npx skills add facioquo/stock-indicators-dotnet --skill code-completion -a codex`. Or copy the skill folder (.agents/skills/code-completion in facioquo/stock-indicators-dotnet) into .agents/skills/code-completion in your project. Codex loads it when a task matches its description.

Can I use Code Completion in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add facioquo/stock-indicators-dotnet --skill code-completion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-completion, .gemini/skills/code-completion, .github/skills/code-completion and .opencode/skills/code-completion in your project.

What does Code Completion need to run?

Going by SKILL.md and its folder, Code Completion needs the command-line tools its instructions call (dotnet, npx and bash). Our summary lists: Node.js.

Does Code Completion access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Code Completion safe to install?

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.

What licence does Code Completion use?

Code Completion is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Completion use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 855 tokens, read only when the agent opens those files.

What are the alternatives to Code Completion?

Skills that share tags, products or a category with Code Completion: Chrome Devtools MCP (managedcode/dotnet-skills, 486 stars), Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars), Odc Debugging (DouglasNeuroInformatics/OpenDataCapture, 119 stars) and Adk Setup (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Completion?

facioquo (a GitHub organization) maintains it in facioquo/stock-indicators-dotnet, which has 1,247 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

Source: facioquo/stock-indicators-dotnet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.