Skills

Fetch all my skills, programmatically.

The Skill model

The Skill model contains all the information about each skill.

Properties

  • Name
    name
    Type
    string
    Description

    Name of the skill

  • Name
    description
    Type
    string
    Description

    Short description of the skill

  • Name
    type
    Type
    string
    Description

    Type of skill (e.g. api, database, infrastructure, framework, language)

  • Name
    level
    Type
    string
    Description

    The contact display name in the contact list. By default, this is just the username.


GET/api/skills

List all skill

This endpoint allows you to retrieve a list of all my skills.

Optional attributes

  • Name
    only
    Type
    integer
    Description

    Filter by type of skill (e.g. api, database, infrastructure, framework, language)

Request

GET
/v1/contacts
curl -G https://valentinprugnaud.dev/api/skills -d only=api

Example Response

[
  {
    "name": "Stripe",
    "description": "Stripe is hands down my favorite payment processing API and a huge inspiration for developer experience.",
    "type": "api"
  },
  {
    "name": "GitHub",
    "description": "Started using GitHub Actions for CI/CD and never looked back (so long Jenkins!). I also routinely use the GitHub API for automating workflows.",
    "type": "api"
  },
  {
    "name": "Clerk",
    "description": "Got tired of rolling my own auth, so Clerk is a great solution for auth and user management, when Supabase is not enough.",
    "type": "api"
  },
  {
    "name": "Novu",
    "description": "Building a lot of MVPs for various products, rolling my own notifications was a pain. Novu is my go-to now.",
    "type": "api"
  },
  {
    "name": "Resend",
    "description": "Email is also a pain when creating new products regularly. So I use Resend for email marketing and transactional emails. (And sometimes Postmark!)",
    "type": "api"
  }
]

Was this page helpful?