vietnam-crypto-radar
Skill1 starsChanged 27 days agoNo licenceView on GitHub
Produce up-to-date intelligence briefings on Vietnam's crypto/digital-asset landscape — laws, decrees, circulars, licensing, tax, accounting, administrative penalties, the pilot exchange market, local controlled technology trials such as Da Nang's crypto/fiat sandbox, city blockchain schemes (Da Nang's Đề án to 2030 and DNC-Chain), Vietnam's International Financial Centre at Ho Chi Minh City and Da Nang, and enforcement. Use this skill WHENEVER the user asks "what's new with Vietnam crypto," wants a regulatory update, asks about a specific instrument (e.g. the DTI Law, Resolution 05, Decree 284, or a TT-BTC circular), wants to know the status of the pilot/VASP licensing, asks about crypto tax or penalties in Vietnam, or needs a briefing for a partner/investor/founder on the VN digital-asset regime. It also covers the retail/consumer reality (see `references/adoption.md`) — why on-chain adoption is top-5 in the world yet you can't pay rent in USDT, which offshore exchanges Vietnamese people actually use (Binance, OKX, Bybit, Bitget, Gate.io, MEXC), whether crypto is spendable day-to-day, and whether crypto cards (Bitget/OKX/SafePal) work here — and maps the VN Web3 ecosystem players as context (communities, builders, student/education programs, events, flagship projects; see `references/ecosystem.md`). Trigger even when the user doesn't say the word "skill" — phrases like "VN crypto reg," "is X legal in Vietnam now," "Vietnam exchange license," "Vietnam crypto fines," "any movement on the sandbox," "Da Nang crypto sandbox," "Da Nang blockchain plan," "what is DNC-Chain," "can I tokenize RWAs in Vietnam," "what is the Vietnam IFC," "which exchanges are popular in Vietnam," "can I pay with crypto/USDT in Vietnam," "do crypto cards work in Vietnam," "who are the Vietnam web3 communities," or "catch me up on Vietnam digital assets" all apply. Prefer this over answering from memory, because the regime is moving fast and stale answers are worse than no answer.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- business-model-to-marketSkill
- list-telegram-chatsSkill
- llm-wikiSkill
- luma-calendarSkill
- nearby-places-searchSkill
- skill-evolutionSkill
- telegram-group-summarySkill
- telegram-sendSkill
- vietnam-legal-advisorSkill
- vietnam-visa-checkSkill
- web3-legal-agreementsSkill
- web3-opportunitiesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

