Agent skill

Asset It Management

by sickn33 in sickn33/agentic-awesome-skills

Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request.

MITAuto-check passedDocuments & Office

Install Asset It Management

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill asset-it-management -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills asset-it-management --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/asset-it-management .claude/skills/asset-it-management && 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
asset-it-management
GitHub stars
47k
Used in
1 other repo
Token cost
~4k tokens
SKILL.md length
1,469 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Tasks that involve CSV and tabular files
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Asset It Management is an agent skill from sickn33/agentic-awesome-skills. Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request. Use for asset audits.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering CSV and tabular files and SQL. It works with SQL and Notion. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve CSV and tabular files
  • Tasks that involve SQL

Example prompts

  • “/asset-it-management”

Workflow steps

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

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    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

Asset It Management loads about 4k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 1,469 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~4k

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 sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,469 words, ~4,006 tokens.

Download SKILL.mdSave it as .claude/skills/asset-it-management/SKILL.md (or your agent's skills folder).
name
asset-it-management
description
Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request. Use for asset audits.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, onboard
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Asset & IT Management

What it is: Equipment tracking.

Overview

Works out the smallest useful Asset & IT Management setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 3: Onboard. Fits: Growth stage. Table code: n/a.

When to Use This Skill

  • asset tracker
  • it asset management
  • laptop inventory
  • equipment register

Also use it when the user says "equipment tracking", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How many devices does the company own?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • Assets - How many assets? / Laptops, phones or both? / Monitors and other?
  • Assignment - Who assigns? / Signed for or not? / Shared or personal?
  • Tracking - Serial numbers tracked? / Warranty dates? / Insurance?
  • Current process - Where is the list now? / Spreadsheet or none? / What goes missing?
  • Outcome - What do you need? / An inventory, returns or a spend view?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: asset-it-management
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Assets": null
  "Assignment": null
  "Tracking": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Track assets as rows with a serial number and a named holder. Assign on day one, release on exit, and the list stays true.

Why this one: Asset registers fail at handover, not at purchase. Tying every asset to a person and a date is what makes it accurate.

Workflow: Purchase → Assign to person → Store location → Return on exit → Write-off

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

csv
Asset Name,Asset ID,Asset Type,Assigned Date,Assigned To,Linked Accounts,Brand/Model,Condition,Current Value,Department,Location,Notes,Purchase Date,Purchase Value,Currency,Return Date,Serial Number,Status,Warranty Expiry
Example Laptop 14,,Laptop,2026-01-15,Example Employee,"Workspace, VPN",Example Laptop 14 (2023),New,800.00,Delivery,Example City,"Warranty runs to December 2027, so the finance depreciation schedule needs to match.",2026-01-15,1000.00,INR,2026-01-15,SN-EXAMPLE-001,In Use,2027-11-14
sql
CREATE TABLE asset_it_management (
  asset_name VARCHAR(255),
  asset_id SERIAL PRIMARY KEY,
  asset_type VARCHAR(100) NOT NULL,
  assigned_date DATE NOT NULL,
  assigned_to VARCHAR(255),
  linked_accounts VARCHAR(255),  -- relation -> target record
  brand_model VARCHAR(255),
  condition VARCHAR(100) NOT NULL,
  current_value NUMERIC(14,2) NOT NULL,
  department VARCHAR(255),
  location VARCHAR(255),
  notes TEXT,
  purchase_date DATE NOT NULL,
  purchase_value NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  return_date DATE,
  serial_number VARCHAR(255),
  status VARCHAR(100) NOT NULL,
  warranty_expiry DATE NOT NULL,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_asset_it_management_status ON asset_it_management (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Asset & IT Management",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "Asset Name": {
      "type": "string"
    },
    "Asset ID": {
      "type": "integer"
    },
    "Asset Type": {
      "type": "string"
    },
    "Assigned Date": {
      "type": "string",
      "format": "date"
    },
    "Assigned To": {
      "type": "string"
    },
    "Linked Accounts": {
      "type": "string"
    },
    "Brand/Model": {
      "type": "string"
    },
    "Condition": {
      "type": "string"
    },
    "Current Value": {
      "type": "number"
    },
    "Department": {
      "type": "string"
    },
    "Location": {
      "type": "string"
    },
    "Notes": {
      "type": "string"
    },
    "Purchase Date": {
      "type": "string",
      "format": "date"
    },
    "Purchase Value": {
      "type": "number"
    },
    "Currency": {
      "type": "string"
    },
    "Return Date": {
      "type": "string",
      "format": "date"
    },
    "Serial Number": {
      "type": "string"
    },
    "Status": {
      "type": "string"
    },
    "Warranty Expiry": {
      "type": "string",
      "format": "date"
    }
  },
  "required": [
    "Asset Type",
    "Assigned Date",
    "Condition",
    "Current Value",
    "Purchase Date",
    "Purchase Value",
    "Status",
    "Warranty Expiry"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Asset Name | Title | Use as the database title |
| Asset ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Asset Type | Select (add options after import) | Convert to Select, add options: "Laptop", "Monitor", "Phone", "Tablet", "Accessory", "Furniture", "Software License" |
| Assigned Date | Date | Convert to Date |
| Assigned To | Text | Leave as Text |
| Linked Accounts | Relation (link to the target database) | Convert to Relation, link to the target database |
| Brand/Model | Text | Leave as Text |
| Condition | Select (add options after import) | Convert to Select, add options: "New", "Good", "Fair", "Needs Repair", "Retired" |
| Current Value | Number (format: currency) | Convert to Number, set format to Currency |
| Department | Text | Leave as Text |
| Location | Text | Leave as Text |
| Notes | Text | Leave as Text |
| Purchase Date | Date | Convert to Date |
| Purchase Value | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Return Date | Date | Convert to Date |
| Serial Number | Text | Leave as Text |
| Status | Select (add options after import) | Convert to Select, add options: "In Use", "In Stock", "In Repair", "Retired", "Lost" |
| Warranty Expiry | Date | Convert to Date |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

Return Date may be absent before the relevant lifecycle stage or when no verified source exists. Do not invent values to satisfy a schema.

#FieldTypeSQLJSON SchemaNotionCSV example
1Asset NametextVARCHAR(255)stringTextExample Laptop 14
2Asset IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
3Asset TypeselectVARCHAR(100)stringSelect (add options after import)Laptop
4Assigned DatedateDATEstring, format: dateDate2026-01-15
5Assigned TotextVARCHAR(255)stringTextExample Employee
6Linked AccountsrelationVARCHAR(255)stringRelation (link to the target database)Workspace, VPN
7Brand/ModeltextVARCHAR(255)stringTextExample Laptop 14 (2023)
8ConditionselectVARCHAR(100)stringSelect (add options after import)New
9Current ValuecurrencyNUMERIC(14,2)numberNumber (format: currency)800.00
10DepartmenttextVARCHAR(255)stringTextDelivery
11LocationtextVARCHAR(255)stringTextExample City
12Noteslong_textTEXTstringTextWarranty runs to December 2027, so the finance depreciation schedule needs to match.
13Purchase DatedateDATEstring, format: dateDate2026-01-15
14Purchase ValuecurrencyNUMERIC(14,2)numberNumber (format: currency)1000.00
15CurrencytextVARCHAR(255)stringTextINR
16Return DatedateDATEstring, format: dateDate2026-01-15
17Serial NumbertextVARCHAR(255)stringTextSN-EXAMPLE-001
18StatusselectVARCHAR(100)stringSelect (add options after import)In Use
19Warranty ExpirydateDATEstring, format: dateDate2027-11-14
Show full SKILL.md (502 more words)Show less

Select Options

Asset Type

Laptop | Monitor | Phone | Tablet | Accessory | Furniture | Software License

Condition

New | Good | Fair | Needs Repair | Retired

Status

In Use | In Stock | In Repair | Retired | Lost

Relations

Link fields: Linked Accounts

Examples

Prompt

Laptops keep disappearing after people leave and we cannot find them.

Context first - one question per message, nothing already answered:

Q: Do you track serial numbers? A: No.

Q: Who assigns? A: IT, on day one.

Q: How many assets? A: About 40.

Recommended next step - offered, not built:

Track assets as rows with a serial number and a named holder. Assign on day one, release on exit, and the list stays true.

Workflow: Purchase → Assign to person → Store location → Return on exit → Write-off

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute payroll, tax, leave balances or KPIs.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not image devices, wipe them or enforce MDM policy.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.
  • Module Catalog - find the relevant module, then read its skill.
  • @people-directory - the employee master record most modules link to.
  • @notification-reminder-hub - turns due dates in this module into reminders.

Reusable Prompt

I want to set up equipment tracking for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.

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

Files

Just SKILL.md in skills/asset-it-management of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Asset It Management 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.

Asset It Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Asset It Management this skillsickn33/agentic-awesome-skills47k1 repos~4kAutomated safety check: PassMIT
Data Exploreamd/gaia1.6k—~633Automated safety check: PassMIT
Exportai-analyst-lab/ai-analyst304—~3.8kAutomated safety check: PassMIT
Data Processingjeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Rust SQL Testshencangsheng/easydb_app590—~1.2kAutomated safety check: PassMIT
Mendix Odata Pushdownmendixlabs/mxcli129—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Data Explore

    amd/gaia

    Load messy tabular data into SQL scratchpad tables and answer questions with real queries instead of eyeballing.

    1.6k GitHub stars~633 tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Export

    ai-analyst-lab/ai-analyst

    Export analysis results in different formats for different audiences — email summaries, Slack updates, decision briefs, Google Docs with embedded charts, Word documents, slide decks, or raw data CSVs.

    304 GitHub stars~3.8k tokensUpdated 10 days ago
    Documents & OfficeAuto-check passed
  • Data Processing

    jeremylongshore/tons-of-skills-marketplace

    A skill your agent uses when working with structured data files (CSV, JSON, YAML, TOML, Parquet) — querying, transforming, filtering, aggregating, or converting between formats

    2.8k GitHub stars~1.3k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Rust SQL Test

    shencangsheng/easydb_app

    Enforces unit test requirements for the Rust data-processing modules in src-tauri/src/sql/ (generator.rs, parse.rs) and src-tauri/src/reader/ (excel.rs and other readers).

    590 GitHub stars~1.2k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Mendix Odata Pushdown

    mendixlabs/mxcli

    Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…

    129 GitHub stars~2.5k tokensUpdated today
    DatabasesAuto-check passed
  • Forge Codegen Crud

    yaomindong1996/forge-admin

    Generate or review Forge project code-generation output for CRUD modules.

    126 GitHub stars~1.3k tokensUpdated today
    Documents & OfficeAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Questions about Asset It Management

What does Asset It Management do?

Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request. Asset It Management is an agent skill from sickn33/agentic-awesome-skills. Asset and IT register: serial, model, condition, assignee, location, purchase value, warranty expiry and return date, as CSV, SQL, JSON Schema or Notion on request.

When should I use Asset It Management?

Asset It Management fits situations like: tasks that involve CSV and tabular files; tasks that involve SQL.

How do I install Asset It Management in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill asset-it-management -a claude-code`. Or copy the skill folder (skills/asset-it-management in sickn33/agentic-awesome-skills) into .claude/skills/asset-it-management in your project. Claude Code loads it when a task matches its description.

How do I install Asset It Management in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill asset-it-management -a codex`. Or copy the skill folder (skills/asset-it-management in sickn33/agentic-awesome-skills) into .agents/skills/asset-it-management in your project. Codex loads it when a task matches its description.

Can I use Asset It Management 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 sickn33/agentic-awesome-skills --skill asset-it-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/asset-it-management, .gemini/skills/asset-it-management, .github/skills/asset-it-management and .opencode/skills/asset-it-management in your project.

What does Asset It Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Asset It Management is instructions for the agent only.

Does Asset It Management access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Asset It Management 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 Asset It Management use?

Asset It Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Asset It Management use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Asset It Management?

Skills that share tags, products or a category with Asset It Management: Data Explore (amd/gaia, 1.6k stars), Export (ai-analyst-lab/ai-analyst, 304 stars), Data Processing (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Rust SQL Test (shencangsheng/easydb_app, 590 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Asset It Management?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.