Why I Added a Skills Index to My Website

My work now includes a bilingual website, reusable AI-assisted workflows and a product I am still developing. I wanted someone visiting my site to understand what I actually contribute to those projects: which problem I take on, how I work through it and what I can show for it.

I come from a business and marketing background, with experience in retail, e-commerce and education marketing. I did not start with a traditional coding background. As the work has changed, I have learned new tools and used AI-assisted development to build things I wanted to put into practice.

That creates a practical communication problem. A project page can show a finished result, while a list of tools can show what I use. The connection between the two still needs explaining. I added Skills in Practice, the skills index on my website, to make that connection visible.

Give a visitor a way into the work

The page groups my work into 15 capabilities, including content planning, customer research, website information architecture, bilingual localization and AI content workflows. A visitor can start with the kind of work they want to understand, then open an entry for more detail.

Each entry follows the same useful questions:

• Scope and deliverables: What work does this cover, and what would I produce?
• How I work: How do I approach the problem?
• My role and delivered work: What have I actually been responsible for, and where can someone inspect it?

I chose that structure because a broad skill label leaves a lot unsaid. “Content planning” could cover choosing topics, organizing evidence, preparing a brief or coordinating material across channels. The detail gives the visitor a clearer basis for deciding which part of my experience is relevant.

The entries describe areas of work. They are not a set of certifications, and they do not map one-to-one to the public Skill repositories linked from the page.

Explain what I take responsibility for

AI-assisted building makes it especially important to explain my role clearly.

For my website, my work includes deciding how information should be organized and how the English and Chinese content should connect. For Tap to Share, it includes defining merchant and customer flows, requirements and the quality expected of generated suggestions. I use AI tools and Codex to help carry those decisions into implementation.

I still need to work out what the result should do, check whether it behaves that way, investigate problems and decide what needs to change. Factual verification, business judgment and final decisions remain my responsibility. Learning enough about the tools to direct and test the work is part of that responsibility too.

This is the ownership I want the page to show: following a problem through decisions, implementation and review. Describing those contributions lets me present the work honestly from my business and marketing background, without implying that I hand-coded every part or have a traditional software-engineering background.

Let a capability lead to something inspectable

The AI Content Workflow Design entry is one example. It explains the work in terms of inputs, handoffs, reusable instructions and review points. It then links to the article about turning my writing workflow into a Skill and a public workflow repository.

Those links give the capability a more concrete meaning. Someone can look at an actual piece of work, read the process behind it and see what the reusable material covers. They can also decide whether it is relevant to their own question.

I have been turning repetitive standard operating procedures into workflows and Skills because I want useful decisions and checks to survive beyond one task. The index gives that work a place in the wider portfolio. A reusable workflow becomes one piece of evidence alongside the project and the delivered content.

Some workflows stay private because they include additional working context and data connections. My Opportunity Engine work supports private opportunity discovery, evidence organization and content decisions, and remains in development and validation. The index can explain that purpose and my role without exposing its internal implementation.

Keep the limits beside the evidence

Different projects support different statements about what I have delivered. My bilingual website is published and can be explored directly. Tap to Share is still in development and testing, including testing by paying merchants. Its case study explains the product and my contribution; that stage does not establish broad adoption or proven business results. The Tap to Share marketing website is now live, while the paid pilot and product iteration continue.

I want those distinctions to remain visible when someone moves from a capability to its evidence. A page is more useful when it says what a project currently supports than when every entry sounds equally complete.

The public GitHub links also need a clear boundary. I am still organizing the licensing terms for my original public Skills, and I do not permit their commercial use. Some workflows adapt material from other repositories, whose sources and terms still matter. Anyone considering reuse should check each repository's README, license and upstream terms. Public access does not itself mean that every workflow is open source or available for unrestricted use.

Make a more specific conversation possible

I built the index for people who may want to work with me, as well as people who are curious about how I work. A recruiter can start with a capability relevant to a role and follow it to a case. A collaborator can look at the scope and deliverables before discussing where I might contribute.

The page also gives feedback a more specific starting point. I would rather discuss a particular method, responsibility or missing piece of evidence than leave someone with a general impression that I use a lot of tools.

For me, visibility means making the work and my part in it available to inspect. The Skills Index gives a visitor a route into that evidence. If an entry connects with a problem you are working on, I would welcome a conversation about it.