Your reporting is most likely to be done in the least of the child tables. I would allow experience and skills to reside in the same table as use of skills spawns experience.
Pull lookup fields into your child table from the main parent table << those you're likely to search.
Customize the dedicated search box to search the least child for all the attributes you're likely to search for.
Another approach is to create an "Ask The User" report, which when run, asks you for values to enter for the search criteria.
Where Years of experience is equal to _______
Where skill set is equal to ______
Where Department is equal to _______
After entering the criteria, you'd click the go button or search button and it pulls according to what you've entered.
It is not recommended that you perform one search action and search all fields in your entire app.
What I'm suggesting is configuring your custom search box to search only the fields that contain, for example, "years of experience", "Department", "Skills". You can use AND and OR logic in your custom search boxes.
I believe your logical operators have to be in upper case.
I'm afraid I do not understand where Quick Base Actions come into this.
A Quick Base Action is usually for automatic record creation in another table, or, in another app upon the creation or modifying of a record that meets a certain criteria to perform that QB Action.
Can you help clarify for me?
Essentially -- performance, although there may be more technical reasons. But, if it could be accomplished, and perhaps it can, such a demanding search would cause performance issues to arise such as long wait for results and ultimate time out. So you're limited to searching one table using the customizable boxes.
Now, while on the Home page, you can click the magnifying glass icon at the top right and perform a broad search across the entire app. Try it out and see how performance goes. You will be presented with links to tips on how to improve your search.